From: Nicholas Miell <nmiell@comcast.net>
To: Andi Kleen <ak@suse.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org, gk@garethknight.com
Subject: Re: [PATCH] generic signal code (small new feature - userspace signal mask), kernel 2.6.16
Date: Mon, 16 Oct 2006 16:15:37 -0700 [thread overview]
Message-ID: <1161040537.2379.3.camel@entropy> (raw)
In-Reply-To: <p731wp8e6ew.fsf@verdi.suse.de>
On Mon, 2006-10-16 at 15:28 +0200, Andi Kleen wrote:
> Linus Torvalds <torvalds@osdl.org> writes:
> >
> > Why? You're doing user-space accesses from within critical sections with a
> > spinlock, and that's just a big no-no. Think page faults, swapping etc.
>
> He could pin the page in memory like futexes do. One page pinned
> per thread shouldn't be a big DOS issue either.
>
> -Andi
Whatever the final solution ends up being (assuming this actually goes
somewhere), it should be extensible enough for other uses (for example,
some sort of "please don't preempt me right now" hint for use with
pthread spinlocks.)
--
Nicholas Miell <nmiell@comcast.net>
next prev parent reply other threads:[~2006-10-16 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 3:04 [PATCH] generic signal code (small new feature - userspace signal mask), kernel 2.6.16 Gareth Knight
2006-10-16 3:37 ` Linus Torvalds
2006-10-16 3:50 ` Gareth Knight
2006-10-16 13:28 ` Andi Kleen
2006-10-16 23:15 ` Nicholas Miell [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-17 9:24 linux
2006-10-17 12:32 ` Gareth Knight
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=1161040537.2379.3.camel@entropy \
--to=nmiell@comcast.net \
--cc=ak@suse.de \
--cc=gk@garethknight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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