 | | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c —Michael Martelli
|
| | | Nevermind, I figured out the error after I posted and reviewed my code again. Thanks anyway... (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| | | |
| | | | | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c —Michael Obenland
|
| | | | (...) Fine. Could you please post the solution? I don't like unsolved riddles :) Regards, Michael (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c —Michael Martelli
|
| | | | (...) Sure thing sorry, the problem was that I had the wrong variable in one of the if statement, I copied it over wrong from my hand-written notes I made of the Alg ===...=== void *malloc(size_t size) { size_t *ptr,*next, bestSize, *mm_best_free; (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c —Mark Riley
|
| | | | (...) BTW, you can delete these two lines of intialization (i.e. lines 12 & 15 in the above function) as the intialized value gets clobbered on finding the first suitable sized block: 12) mm_best_free=ptr; 15) mm_best_free++; //this must point to (...) (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c —Michael Martelli
|
| | | | (...) Yeah, very true. Those lines where in there becuase of the error I originally had in my code, but since my code changed (and is correct) those lines are not needed). Thanks Mike (21 years ago, 6-Dec-03, to lugnet.robotics.rcx.legos)
|
| | | | |
