From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <5176869C.6030907@xenomai.org> Date: Tue, 23 Apr 2013 15:03:24 +0200 From: Philippe Gerum MIME-Version: 1.0 References: <201304191346.38739.leo@alaxarxa.net> <517195B6.8020209@xenomai.org> <12ABCC03-FADF-4C5A-9CAE-CD9E5CA63A19@mah.priv.at> <51724F82.2000809@web.de> <5172B0E5.7090806@xenomai.org> <5172B1B5.10804@web.de> <5172B28C.6070503@xenomai.org> <5172B3CD.20007@web.de> <5172B4AA.1060704@xenomai.org> <5174E2A0.1040906@siemens.com> <51752114.7040903@xenomai.org> <51753E59.4090609@siemens.com> <51758816.4050100@xenomai.org> <51764485.9020403@siemens.com> <51766E65.1010304@xenomai.org> <5176813B.9030404@xenomai.org> <517684C3.2090607@siemens.com> In-Reply-To: <517684C3.2090607@siemens.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] Default options in the debian package List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: "xenomai@xenomai.org" On 04/23/2013 02:55 PM, Jan Kiszka wrote: > 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. :) > Agreed. -- Philippe.