Hi Andrew
The PREEMPT_RT patch makes the kernel fully pre-emptive (leading to
improved maximum latency) and adds support for priority inheritance
mutexes. There are no user space API changes, the code to use
_POSIX_THREAD_PRIORITY_SCHEDULING and _POSIX_THREAD_PRIO_INHERIT is
already in libCom (if disabled by default). I'd like to use the
epicsMessageQueue from a high priority thread but the send and receive
functions may calloc an eventNode, and that might cause a page fault or
block my thread on the malloc lock. I'd like to be able to pre-allocate
the eventNodes because I know the maximum number of threads that may
wait on the queue in advance.
James
> -----Original Message-----
> From: Andrew Johnson [mailto:[email protected]]
> Sent: 28 January 2011 15:50
> To: [email protected]
> Cc: Rowland, James (DLSLtd,RAL,DIA)
> Subject: Re: epicsMessageQueue Linux PREEMPT_RT
>
> Hi James,
>
> On Friday 28 January 2011 06:48:54 [email protected] wrote:
> >
> > I'd like to use the epicsMessageQueue on Linux PREEMPT_RT, but the
> event
> > nodes are calloc'ed at runtime. I can fill up the event node free
> list
> > by creating some dummy threads at initialization, is there interest
> in a
> > patch to add a call for this pre-allocation on Linux?
>
> You've lost me, I know very little (assume nothing) about what's
> different
> with Linux PREEMPT_RT. Can you explain more what you're trying to do
> and how
> our existing code is deficient for that purpose.
>
> - Andrew
> --
> If a man is offered a fact which goes against his instincts, he will
> scrutinize it closely, and unless the evidence is overwhelming, he
will
> refuse to believe it. If, on the other hand, he is offered something
> which affords a reason for acting in accordance to his instincts, he
> will accept it even on the slightest evidence. -- Bertrand Russell
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
- Replies:
- Re: epicsMessageQueue Linux PREEMPT_RT Eric Norum
- Re: epicsMessageQueue Linux PREEMPT_RT Andrew Johnson
- References:
- epicsMessageQueue Linux PREEMPT_RT james.rowland
- Re: epicsMessageQueue Linux PREEMPT_RT Andrew Johnson
- Navigate by Date:
- Prev:
Re: epicsMessageQueue Linux PREEMPT_RT Eric Norum
- Next:
Re: OMS VS4 "omsPut: card 0 send ring full!" Nerses Gevorgyan
- 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:
Re: epicsMessageQueue Linux PREEMPT_RT Andrew Johnson
- Next:
Re: epicsMessageQueue Linux PREEMPT_RT Eric Norum
- 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
|