Subject: |
epicsThread priority / a world beyond EPICS |
From: |
Till Straumann <[email protected]> |
To: |
"EPICS (E-mail)" <[email protected]> |
Date: |
Mon, 11 Nov 2002 14:35:09 -0800 |
I have an application with hard real-time demands
and I want to make sure it has a higher priority
than any of EPICS' threads.
Wouldn't it make sense to have a range of priorities
who are guaranteed to be unused by EPICS?
E.g. have
epicsThreadPriorityMax = 95
epicsThreadPriorityMaxMax = 99
and EPICS still checking that itself is never using
a priority > epicsThreadPriorityMax.
epicsThreadMaxMax would then be reserved for user
tasks.
Second question: if I create such a high priority
thread (currently not by using EPICS OSI but a generic
RTEMS call) - I guess it should be safe for that thread
to call EPICS primitives who are safe to call from IRQ context
(such as 'callbackRequest()'), right?
-- Till.
- Navigate by Date:
- Prev:
Re: Extensions problem Andrew Johnson
- Next:
Extensions problem Krishna Arya
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
<2002>
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Extensions problem Krishna Arya
- Next:
EPICS Meeting Karen White
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
<2002>
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|