ok guys I and my friend are trying to write an operatingsystem and were going through the code of linux MM and discovered that linux used the same virtual space
i.e only one page directory for all its processes including the kernel space. though there is segment level protection in this approach we are leaning towards a seperate page directory for each process giving obvious page level protection too and it makes it way easier to deal with page replacement algorithms. which do u think is better the linux approach or ours and which do u think is easier. Please give your views on this subject any criticism is also most welcome.
Linux MM Is It Good for us?
- Pype.Clicker
- Member
- Posts: 5964
- Joined: Wed Oct 18, 2006 2:31 am
- Location: In a galaxy, far, far away
- Contact:
Re:Linux MM Is It Good for us?
only one page directory in Linux ? i guess you're not reading the latest kernel, then, because in the code for thread switch i saw from Linux, there was a "mov cr3, [next_thread->process->CR3_copy], or something alike ...
moreover, i know Linux uses copy on write, which seems hard to set up without paging ... and finally, i don't think there's that much segmented protection because it isn't even possible for it to discover you're executing something that is on the stack.
moreover, i know Linux uses copy on write, which seems hard to set up without paging ... and finally, i don't think there's that much segmented protection because it isn't even possible for it to discover you're executing something that is on the stack.