Project 3: Malloc and FreeImportant DatesQuestions about the project? Send them to Final Deadline: Monday 02/28 @ 9pm. ClarificationsYou should set m_error not merror (corrected below). NEW: When debugging is on, Mem_Alloc should:
ObjectivesThere are three objectives to this assignment:
OverviewIn this project, you will be implementing a memory allocator for the heap of a user-level process. Your functions will be to build your own malloc() and free(). Memory allocators have two distinct tasks. First, the memory allocator asks the operating system to expand the heap portion of the process's address space by calling either sbrk or mmap. Second, the memory allocator doles out this memory to the calling process. This involves managing a free list of memory and finding a contiguous chunk of memory that is large enough for the user's request; when the user later frees memory, it is added back to this list. This memory allocator is usually provided as part of a standard library and is not part of the OS. To be clear, the memory allocator operates entirely within the virtual address space of a single process and knows nothing about which physical pages have been allocated to this process or the mapping from logical addresses to physical addresses. When implementing this basic functionality in your project, we have a few
guidelines. First, when requesting memory from the OS, you must use mmap()
(which is easier to use than sbrk()). Second, although a real memory allocator
requests more memory from the OS whenever it can't satisfy a request from the
user, your memory allocator must call mmap() only one time (when it is first
initialized). Classic malloc() and free() are defined as follows:
For simplicity, your implementations of Mem_Alloc(int size) and Mem_Free(void *ptr) should basically follow what malloc() and free() do; see below for details. You will also provide a supporting function, Mem_Dump(), described below; this routine simply prints which regions are currently free and should be used by you for debugging purposes. Program SpecificationsFor this project, you will be implementing several different routines as part of a shared library. Note that you will not be writing a main() routine for the code that you handin (but you should implement one for your own testing). We have provided the prototypes for these functions in the file mem.h (which is available at ~cs537-1/public/mem.h); you should include this header file in your code to ensure that you are adhering to the specification exactly. You should not change mem.h in any way! We now define each of these routines more precisely.
You must provide these routines in a shared library named "libmem.so". Placing the routines in a shared library instead of a simple object file makes it easier for other programmers to link with your code. There are further advantages to shared (dynamic) libraries over static libraries. When you link with a static library, the code for the entire library is merged with your object code to create your executable; if you link to many static libraries, your executable will be enormous. However, when you link to a shared library, the library's code is not merged with your program's object code; instead, a small amount of stub code is inserted into your object code and the stub code finds and invokes the library code when you execute the program. Therefore, shared libraries have two advantages: they lead to smaller executables and they enable users to use the most recent version of the library at run-time. To create a shared library named libmem.so, use the following commands (assuming your library code is in a single file "mem.c"): gcc -m32 -c -fpic mem.c gcc -m32 -shared -o libmem.so mem.o Note that you should compile with -m32 to make sure your binary is a 32-bit binary. To link with this library, you simply specify the base name of the library with "-lmem" and the path so that the linker can find the library "-L.". gcc -m32 -lmem -L. -o myprogram mymain.c Of course, these commands should be placed in a Makefile. Before you run "myprogram", you will need to set the environment variable, LD_LIBRARY_PATH, so that the system can find your library at run-time. Assuming you always run myprogram from this same directory, you can use the command:
setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:.
If the setenv command returns an error "LD_LIBRARY_PATH: Undefined variable", do not panic. The error implies that your shell has not defined the environment variable. In this case, you simply need to run: setenv LD_LIBRARY_PATH . Unix HintsIn this project, you will use mmap to map zero'd pages (i.e., allocate new pages) into the address space of the calling process. Note there are a number of different ways that you can call mmap to achieve this same goal; we give one example here:
// open the /dev/zero device
int fd = open("/dev/zero", O_RDWR);
// sizeOfRegion (in bytes) needs to be evenly divisible by the page size
void *ptr = mmap(NULL, sizeOfRegion, PROT_READ | PROT_WRITE, MAP_PRIVATE, fd, 0);
if (ptr == MAP_FAILED) { perror("mmap"); exit(1); }
// close the device (don't worry, mapping should be unaffected)
close(fd);
return 0;
GradingYour implementation will be graded on functionality. However, we will also be comparing the performance of each of your projects; the details for the performance challenge will be coming out soon. Handing in your CodeHand in your source code and a README file. The usual place: ~cs537-1/handin/NAME/p3/, where NAME is your login name. You should copy all of your source files (*.c and *.h) and a Makefile to your p3 handin directory. Do not submit any .o files. |