From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
"'mingo@redhat.com'" <mingo@redhat.com>,
"'Mark Mielke'" <mark@mark.mielke.cc>,
linux-kernel@vger.kernel.org
Subject: Re: Users locking memory using futexes
Date: Tue, 12 Nov 2002 17:36:42 +0000 [thread overview]
Message-ID: <20021112173642.GA14034@bjl1.asuk.net> (raw)
In-Reply-To: <A46BBDB345A7D5118EC90002A5072C7806CAC921@orsmsx116.jf.intel.com>
Perez-Gonzalez, Inaky wrote:
> Good thing is - I just found out after reading twice - that FUTEX_FD does
> not lock the page in memory, so that is one case less to worry about.
Oh yes it does - the page isn't unpinned until wakeup or close.
See where it says in futex_fd():
page = NULL;
out:
if (page)
unpin_page(page);
Rusty's got a good point about pipe() though.
Btw, maybe GnuPG can use this "feature" to lock it's crypto memory in RAM :)
-- Jamie
next prev parent reply other threads:[~2002-11-12 17:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 5:56 Users locking memory using futexes Perez-Gonzalez, Inaky
2002-11-12 17:36 ` Jamie Lokier [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-12 17:57 Perez-Gonzalez, Inaky
2002-11-12 19:17 ` Jamie Lokier
2002-11-12 4:16 Perez-Gonzalez, Inaky
2002-11-12 5:21 ` Jamie Lokier
2002-11-12 9:11 ` Ingo Molnar
2002-11-12 17:40 ` Jamie Lokier
2002-11-11 20:28 PROT_SEM + FUTEX Perez-Gonzalez, Inaky
2002-11-12 3:46 ` Users locking memory using futexes Jamie Lokier
2002-11-12 17:17 ` Rusty Russell
2002-11-12 18:06 ` Alan Cox
2002-11-12 18:13 ` Rusty Russell
2002-11-13 14:27 ` 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=20021112173642.GA14034@bjl1.asuk.net \
--to=lk@tantalophile.demon.co.uk \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mark.mielke.cc \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
/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