Hi Ralph,
On 11/23/2015 03:54 PM, Ralph Lange wrote:
> You're definitely right in this case, but when you use the
> appropriate configuration (from our wiki), you'll be facing that same
> issue without being root.
>
> I guess we never thought about this memlocking thing being done when
> you start a client on a real-time system. Doesn't make much sense to
> memlock, but running a client on a real-time system is certainly
> legal.
I was never completely happy with this mlockall() solution but didn't
really know why until now. On Solaris the IOC and all our test programs
print the message "Unable to lock the virtual address space using
mlockall" to stderr from the same block of code, which I would also like
a solution for.
I think it probably makes more sense for the application itself (i.e.
the IOC's startup script) to explicitly ask for mlockall() to be called,
but I don't know whether we could implement that level of change in 3.15.
- Andrew
--
Light thinks it travels faster than anything but it is wrong.
No matter how fast light travels, it finds the darkness has
always got there first, and is waiting for it.
-- Terry Pratchett, Reaper Man
- Replies:
- Re: Successfully locked memory using mlockAll Michael Davidsaver
- Navigate by Date:
- Prev:
stupid git trick Michael Davidsaver
- Next:
Re: Successfully locked memory using mlockAll Michael Davidsaver
- Index:
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:
stupid git trick Michael Davidsaver
- Next:
Re: Successfully locked memory using mlockAll Michael Davidsaver
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
|