Process vs Task model benefits for RTOS-mainly vxworks!-Let me understand this plz!

Hello,

There were some great white papers written up to explain Wind Rivers memory and process model in 6.0.

Your local Account Team can also provide you with benchmarks regarding the MMU overhead w.r.t. context switching. Realize that the kernel is always mapped into your local context so it's not like you have to load all the TLB entries when moving between RTPs...only the user level pages have to be loaded/unloaded; the overhead I've see is minimal on all PPC architecture especially when compared to the savings in development / maintenance when problems occur.

Jamie

ssubbarayan wrote:

Try the following short cuts, if they don't work than search off the main

I get:

Error - The server has experienced an error. Try again, or contact your Portal administrator if you continue experiencing problems.

Problem?

Jon

Those are both the same link. But they do work for one of the papers (not the other one.) Thanks.

Jon

You might be able to achieve an effect similar to 5.5 by running all your threads in _one_ process. After all,

In my humble opinion, and still after reading the white papers, it is just a means for lazy or incapable programmers, which adds overhead. You can develop your code with the MMU on and after some testing and verifying, that there is no memory violation (program error) you can switch the MMU off and after the final testing ship your product without the unnecessary overhead. I wish I could do the same thing with Linux:)

Regards, Robert