From: Tom Rini <trini@kernel.crashing.org>
To: Amol Kumar Lad <amolk@ishoni.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mlockall() with MCL_FUTURE
Date: Tue, 29 Oct 2002 08:01:41 -0700 [thread overview]
Message-ID: <20021029150141.GD688@opus.bloom.county> (raw)
In-Reply-To: <1035940307.2256.25.camel@amol.in.ishoni.com>
On Tue, Oct 29, 2002 at 08:11:46PM -0500, Amol Kumar Lad wrote:
> Hi,
> I was just going through its implementation. If mlockall() is invoked
> with MCL_FUTURE, does it mean that all the existing locked mappings of
> process should get unlocked ? Attaching code segment from do_mlockall().
> I am using 2.4.18 kernel
There is a problem here which is fixed in 2.4.19, I believe.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2002-10-29 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 1:11 mlockall() with MCL_FUTURE Amol Kumar Lad
2002-10-29 15:01 ` Tom Rini [this message]
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=20021029150141.GD688@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=amolk@ishoni.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.