> Gurus,
> Till vxworks5.5,windriver guys have been using task based model in flat
> address mode for application scheduling,but now with vxworks 6.0
> windriver is playing with idea of using process model over tasks.
> My question is what could be rational behind this?AFAIK,there were not
> much of problems with task models and only advantage of going for
> process model is enabling memory protection.But the adverse effect of
> this would be timing impact due to MMU calculations every time context
> switch happens and Windriver accepts there is performance hit in terms
> of timing but still its deterministic.I am not able to understand how
> this would be deterministic?And how far we can benefit from memory
> protected applications?Because prior versions of vxworks were able to
> achieve good performance even with out memory protection.
>
> Guys using Linux whats your opinion on this?
>
> Can some one explain me this?
>
> Regards,
> s.subbarayan
>
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
---
Robert Berger
Embedded Systems Software Group Leader
INTRACOM S.A.
Hellenic Telecommunications & Electronics Industry
Content Delivery Systems Department
P.O. Box 68, 19.5 km Markopoulo Ave. (Building A)
190 02 Peania, Athens, GREECE
Tel.: (+30 210) 667 4353, 667 9000
Fax.:(+30 210) 667 7101
email: rber@intracom.gr
URL: www.intracom.gr
---
...Under a government which imprisons any unjustly, the true place for a
just man is also a prison. -- Henry David Thoreau
My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
The information contained in this e-mail and in any attachments is
confidential and is designated solely for the attention of the intended
recipient(s). If you are not an intended recipient, you must not use,
disclose, copy, distribute or retain this e-mail or any part thereof.
If you have received this e-mail in error, please notify the sender by
return e-mail and delete all copies of this e-mail from your computer
system(s).
Reply by ●August 11, 20052005-08-11
ssubbarayan wrote:
> Gurus,
> Till vxworks5.5,windriver guys ...
<snip>
You might be able to achieve an effect similar to 5.5
by running all your threads in _one_ process. After all,
5.5 is just one big anonymous process that contains
all those 5.5 threads.
Reply by Jonathan Kirwan●August 10, 20052005-08-10
On 10 Aug 2005 08:39:39 -0700, "Jamie" <jamiehelmer@hotmail.com>
wrote:
I get:
Error - The server has experienced an error. Try again, or contact
your Portal administrator if you continue experiencing problems.
Problem?
Jon
> Gurus,
> Till vxworks5.5,windriver guys have been using task based model in flat
> address mode for application scheduling,but now with vxworks 6.0
> windriver is playing with idea of using process model over tasks.
> My question is what could be rational behind this?AFAIK,there were not
> much of problems with task models and only advantage of going for
> process model is enabling memory protection.But the adverse effect of
> this would be timing impact due to MMU calculations every time context
> switch happens and Windriver accepts there is performance hit in terms
> of timing but still its deterministic.I am not able to understand how
> this would be deterministic?And how far we can benefit from memory
> protected applications?Because prior versions of vxworks were able to
> achieve good performance even with out memory protection.
>
> Guys using Linux whats your opinion on this?
>
> Can some one explain me this?
>
> Regards,
> s.subbarayan
Reply by ssubbarayan●August 10, 20052005-08-10
Gurus,
Till vxworks5.5,windriver guys have been using task based model in flat
address mode for application scheduling,but now with vxworks 6.0
windriver is playing with idea of using process model over tasks.
My question is what could be rational behind this?AFAIK,there were not
much of problems with task models and only advantage of going for
process model is enabling memory protection.But the adverse effect of
this would be timing impact due to MMU calculations every time context
switch happens and Windriver accepts there is performance hit in terms
of timing but still its deterministic.I am not able to understand how
this would be deterministic?And how far we can benefit from memory
protected applications?Because prior versions of vxworks were able to
achieve good performance even with out memory protection.
Guys using Linux whats your opinion on this?
Can some one explain me this?
Regards,
s.subbarayan