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 05:21:13 +0000 [thread overview]
Message-ID: <20021112052113.GA12452@bjl1.asuk.net> (raw)
In-Reply-To: <A46BBDB345A7D5118EC90002A5072C7806CAC920@orsmsx116.jf.intel.com>
Perez-Gonzalez, Inaky wrote:
> This raises a good point - I guess we should be doing something like
> checking user limits (against locked memory, 'ulimit -l').
If futexes are limited by user limits, that's going to mean some
threading program gets a surprise when too many threads decide to
block on a resource. That's really nasty. (Of course, a program can
get a surprise due to just running out of memory in sys_futex() too,
but that's much rarer).
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.
-- Jamie
next prev parent reply other threads:[~2002-11-12 5:14 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 [this message]
2002-11-12 9:11 ` Ingo Molnar
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=20021112052113.GA12452@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
Powered by JetHome