Académique Documents
Professionnel Documents
Culture Documents
http://fixunix.com/vxworks/331795-linux-vs-vxworks.html. It is a
snapshot of the page as it appeared on 20 May 2011 04:56:46 GMT. The
current page <http://fixunix.com/vxworks/331795-linux-vs-vxworks.html>
could have changed in the meantime. Learn more
<http://www.google.com/intl/en/help/features_list.html#cached>
Full version
<http://webcache.googleusercontent.com/search?
q=cache:7vFPRWMO83wJ:fixunix.com/vxworks/331795-linux-vs-
vxworks.html+linux+vs+vxworks&hl=en&client=firefox-a&gl=uk&strip=0>
These search terms are highlighted: linux vs vxworks
Unix Linux Forum - Fixunix.com </>
* Help <http://fixunix.com/faq.php>
*
Remember Me?
------------------------------------------------------------------------
* Forum <http://fixunix.com/forum.php>
o FAQ <http://fixunix.com/faq.php>
o Calendar <http://fixunix.com/calendar.php>
o Community <javascript://>
+ Groups <http://fixunix.com/groups/>
+ Albums <http://fixunix.com/members/albums.html>
+ Member List <http://fixunix.com/members/list/>
o Forum Actions <javascript://>
+ Mark Forums Read
<http://fixunix.com/forumdisplay.php?
do=markread&markreadhash=guest>
* Home <http://fixunix.com/index.php>
* Forum <http://fixunix.com/forum.php>
* OS Forums <http://fixunix.com/forum.php#os-forums>
* Other OS <http://fixunix.com/other-os/>
* *VxWorks* <http://fixunix.com/vxworks/>
* *Linux* *Vs* *vxWorks*
------------------------------------------------------------------------
Results 1 to 4 of 4
LinkBack <javascript://>
Tools <javascript://>
1.
I'm also concerned about the latency of the Real time *Linux* kernels.
Another concerns is educating my resources who are not familiar with
*Linux* much.
Arun
------------------------------------------------------------------------
2.
Re: *Linux* *Vs* *vxWorks*
Hi Arun,
b) Till the time you talk about soft real time it is very subjected to
the context you are talking about. *Linux* is soft real time and
*vxWorks*
is hard real time. In soft real time you can expect a real time
performance but not 100% deterministic. Soft-real time is good enough
for range of application (telecom/consumer device etc); However when
you need a product like robotics, Medical equipment you can't go for
an option which is not deterministc. I have seen people saying that we
need real time OS without knowing exactly their requirement (like
interrupt latency etc acceptable in their application). So you need to
determine based on your application do you really need a hard real
time system If you are not building robotics kind of solution I
believe you will come up with that you need soft real time and then
definetly *linux* is an option for you.
e) *Linux* is royalty free; however with *vxWorks* you need to pay for
production license for each device you sell.
Finally I would say if you have hard real time than *vxWorks* is the
solution; hwoever for soft-real time *linux* is better choice if you
really want to use a wide range of application. If you are limited to
some basic application and not much bothered about royality *vxWorks*
can be good choice to avoid re-educating the resources and some
unforseen issues.
Best Regards
VKG | Ritsoft Technologies
------------------------------------------------------------------------
3.
------------------------------------------------------------------------
4.
Hi,
i don't know if this helps, but altough i love *linux* and i've using
*linux* as my desktop for over 10 years, *vxWorks* has much better
latencies. In a few experiments on the same machine, i measured ISR
latencies of about 1us for a test isr on *vxWorks*, while rtai *linux*
latencies were as high as 30us.
So, IMHO, *linux* is more practical, easy and fast to implement and
would fit most projects. But it is not as good as *vxWorks*.
Rafael
------------------------------------------------------------------------
* Contact Us <mailto:webmaster@fixunix.com>
* Unix *Linux* Forum <http://fixunix.com/>
* Privacy Statement <http://fixunix.com/privacy_policy.php>
* Top <http://fixunix.com/vxworks/331795-linux-vs-vxworks.html#top>