<2002> 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | <2002> 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: base max thread priority |
From: | Marty Kraimer <[email protected]> |
To: | Jeff Hill <[email protected]> |
Cc: | 'Till Straumann' <[email protected]>, 'Eric Norum' <[email protected]>, "'Johnson, Andrew N.'" <[email protected]> |
Date: | Wed, 27 Nov 2002 06:36:38 -0600 |
This is a comment about vxWorks and a question about RTEMS. On vxWorks the following is done: /* Just map osi 0 to 99 into vx 100 to 199 */ /* remember that for vxWorks lower number means higher priority */ /* vx = 100 + (99 -osi) = 199 - osi*/ /* osi = 199 - vx */Since the network tasks, etc all have vxWorks priorities < 100 there is no chance an epics thread can be created with a priortity > important vxWorks threads.
What is the range of priorities for RTEMS?Comment. It seem to me that a system with severe real time requirements should not use BSD style networking. But I guess that the key to implementing severe real time systems is to carefully decide what it must do and don't let it do anything else.
Marty