On 2013-04-23 14:40, Philippe Gerum wrote: >> Well, we have --enable-posix-auto-mlockall for that. But you are right, >> we get rid of all this and enable automatic mlockall for all skins. I do >> not see any drawbacks. >> >> > > From the dept of Xenomai archive: the original intent of controlling > when and how memory locking is done was to address this bug with very > old kernels: > > http://lkml.indiana.edu/hypermail/linux/kernel/0310.0/0649.html > > Back then, apps mmapping I/O space would then mlock(MCL_CURRENT), > mmap(I/O space), then mlock(MCL_FUTURE) to work around this bug manually. >
Interesting - but luckily no longer relevant. :) Jan -- Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
