 | | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
Well, I have another problem - this time with Worst Fit. It may be becuase I have been looking at this code for so much time over the past few months, but I have encountered this problem with my implementation and my mind is boggled (as well as (...) (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Hi Mike, It would be helpful to see each of the memory block dumps and some notation as to what actions you took between each dump (i.e. RCX on/off, program downloaded, etc...) Mark (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Mark, Thanks for the reply, and sorry I forgot to include some more details I have results from 2 memory scans (the values may be a bit off from each other (i.e. starting addresses, but that is becuase they are from 2 times I ran it, and I (...) (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) So, if I understand you correctly, your concern is that the OS tasks move around the first time you power off & on, but not anytime thereafter? Assuming this to be the case, then: 1) When you first download BrickOS, there is a large chunk of (...) (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Mark, Thanks again thanks for the reply. Yes, my main comcern is that the OS tasks move around only after the first power off & on, no time else. And also it was just a typo, the blocks are in order I was looking at the wrong copy of my layout (...) (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) Yes, your summary is correct. Good luck with the rest of your project, Mark (21 years ago, 7-Dec-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: My problems with adding a Best Fit algorithm for memory management to kernel/mm.c
|
|
(...) <snip> (...) <snip> (...) <snip> I didn't have time to mention this in my earlier post, but this memory dump points out a potential problem with the way BrickOS allocates memory for programs. In the above memory dump, the 0x6B words at 0xB648 (...) (21 years ago, 11-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 wrote: [snip] (...) This is easy enough to implement (1 or 2 lines), but raises the question: Should these memory strategies be included with BrickOS (with a config.h flag to control it)? I am sure the educators would rather leave that (...) (21 years ago, 11-Dec-03, to lugnet.robotics.rcx.legos)
|
