<br><div class="gmail_extra"><br><br><div class="gmail_quote">2012/11/1 Mulyadi Santosa <span dir="ltr"><<a href="mailto:mulyadi.santosa@gmail.com" target="_blank">mulyadi.santosa@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi..<br>
<div><br>
On Wed, Oct 31, 2012 at 9:30 PM, Fan Yang <<a href="mailto:lljyangfan@gmail.com" target="_blank">lljyangfan@gmail.com</a>> wrote:<br>
> Hi all:<br>
> I have a problem, if i don't active the page mechanism just use the<br>
> segment mechanism at the x86 cpu, how can I manage the Multi-tasking?<br>
<br>
</div>multitasking and memory management are not directly related IMHO, but<br>
you're right that we need process address space switching.<br>
<br>
I think what you're going to do is already done by Linux kernel port<br>
to non MMU architectures. Can't recall which ones, so try to check<br>
<a href="https://en.wikipedia.org/wiki/Memory_management_unit" target="_blank">https://en.wikipedia.org/wiki/Memory_management_unit</a> for further<br>
examples<br>
<span><font color="#888888"><br>
<br>
-<br>
regards,<br>
<br>
Mulyadi Santosa<br>
Freelance Linux trainer and consultant<br>
<br>
blog: <a href="http://the-hydra.blogspot.com" target="_blank">the-hydra.blogspot.com</a><br>
training: <a href="http://mulyaditraining.blogspot.com" target="_blank">mulyaditraining.blogspot.com</a></font></span></blockquote><div> </div><div>Hi Mulyadi Santosa</div><div> Very honored to see your reply.Yes, the page mechanism can protect different task to interfere each other by mapping different task to different physical memory, and this work is already done by kernel.</div>
<div> </div><div> In order to solve the prev problem I look through the intel manual<a href="http://download.intel.com/design/processor/manuals/253668.pdf" target="_blank">http://download.intel.com/design/processor/manuals/253668.pdf</a> ,and in chapter 3.1 I see this sentence "Segmentation provides a mechanism of isolating individual code, data, and stack modules so that multiple programs (or tasks) can run on the same processor without interfering with one another." then this manual tell me that "There is no mode bit to disable segmentation. The use of paging, however, is optional." that is to say the segment mechanism must be support in the OS, but the page mechanism is optional, but at the manual I can't find any example to explain how to use the single segment mechanism to protect the different tasks to interfere with one another ,so I have a guess you just see.</div>
<div> BTW, I try the 2.6.32.27 kernel version but nothing changed.</div><div><br></div><div>Thanks </div><div>Fan</div>
</div></div><div class="gmail_extra"><span style="color:rgb(136,136,136)"><br>
</span></div>