mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	"'Mark Mielke'" <mark@mark.mielke.cc>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Users locking memory using futexes
Date: Tue, 12 Nov 2002 10:11:46 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0211121000280.5877-100000@localhost.localdomain> (raw)
In-Reply-To: <20021112052113.GA12452@bjl1.asuk.net>


On Tue, 12 Nov 2002, Jamie Lokier wrote:

> It would be nice if the futex waitqueues could be re-hashed against swap
> entries when pages are swapped out, somehow, but this sounds hard.

yes it sounds hard (and somewhat expensive). The simple solution would be
to hash against the pte address, which is an invariant over swapout - but
that breaks inter-process futexes. The hard way would be to rehash the
futex at the pte address upon swapout, and rehash it with the new physical
page upon swapin. The pte chain case has to be careful, and rehashing
should only be done when the physical page is truly unmapped even in the
last process context.

but this should indeed solve the page lockdown problem.

	Ingo


  reply	other threads:[~2002-11-12  7:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12  4:16 Perez-Gonzalez, Inaky
2002-11-12  5:21 ` Jamie Lokier
2002-11-12  9:11   ` Ingo Molnar [this message]
2002-11-12 17:40     ` Jamie Lokier
  -- 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  5:56 Perez-Gonzalez, Inaky
2002-11-12 17:36 ` 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=Pine.LNX.4.44.0211121000280.5877-100000@localhost.localdomain \
    --to=mingo@elte.hu \
    --cc=inaky.perez-gonzalez@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@tantalophile.demon.co.uk \
    --cc=mark@mark.mielke.cc \
    --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

all inboxes | Powered by JetHome®