public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc-Jano Knopp <pub_ml_lkml@marc-jano.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Bug] mlockall() not working properly in 2.6.x
Date: Mon, 19 Dec 2005 12:42:31 +0100	[thread overview]
Message-ID: <20051219114231.GA2830@mjk.myfqdn.de> (raw)
In-Reply-To: <20051219022108.307e68b8.akpm@osdl.org>

On Mon, 19 Dec 2005 at 02:21 (-0800), Andrew Morton wrote:
> Marc-Jano Knopp <pub_ml_lkml@marc-jano.de> wrote:
> >
> > A year ago, I wrote a small mlockall()-wrapper ("noswap") to make
> > certain programs unswappable. It used to work perfectly, until I
> > upgraded to kernel 2.6.x (2.6.13.1 in my case, but that shouldn't
> > matter), which made the mlockall() execute without error, but also
> > without any effect (the "L" in the STAT column of "ps axf" which
> > indicates locked pages is missing).
> > 
> 
> Question is: what kernel version did you upgrade from?

2.4.31. Just rebooted to 2.4.31 and tried again - mlockall() seems to
work perfectly:

# ps axf|grep [9]99
 1037 tty1     SL+    0:00      \_ sleep 999
# uname -a
Linux pc8 2.4.31 #3 Thu Sep 8 16:49:45 CEST 2005 i686 unknown
#


> Prior to 2.4.18 the kernel would allow MCL_FUTURE to propagate into child
> processes.  But that was disabled in 2.4.18 and later.  I seem to recall
> that we did this because inheriting MCL_FUTURE is standards-incorrect.

Oh! So how can I make programs unswappable with kernel 2.6.x then?


Best regards

  Marc-Jano

  reply	other threads:[~2005-12-19 11:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-18 21:21 [Bug] mlockall() not working properly in 2.6.x Marc-Jano Knopp
2005-12-19 10:21 ` Andrew Morton
2005-12-19 11:42   ` Marc-Jano Knopp [this message]
2005-12-19 17:27     ` Jan-Benedict Glaw
2005-12-19 17:47       ` Alan Cox
2005-12-19 18:38         ` Zan Lynx
2005-12-19 19:48           ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051219114231.GA2830@mjk.myfqdn.de \
    --to=pub_ml_lkml@marc-jano.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox