From: Peter Zijlstra <peterz@infradead.org>
To: Rik van Riel <riel@redhat.com>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: KVM bug, git bisected
Date: Mon, 29 Mar 2010 18:44:42 +0200 [thread overview]
Message-ID: <1269881082.12097.359.camel@laptop> (raw)
In-Reply-To: <1269880140.12097.356.camel@laptop>
On Mon, 2010-03-29 at 18:29 +0200, Peter Zijlstra wrote:
> > Peter, would it be safe to increase PREEMPT_BITS to eg. 10?
One reason this all sucks massive is that nesting that many spinlocks
creates a terribly large !preempt section.
There is nothing that stops someone from creating 64k vmas (or more when
someone raises that sysctl) and try this, that's just utter suckage.
next prev parent reply other threads:[~2010-03-29 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 12:43 KVM bug, git bisected Kent Overstreet
2010-03-29 16:11 ` Rik van Riel
2010-03-29 16:27 ` Rik van Riel
2010-03-29 16:29 ` Peter Zijlstra
2010-03-29 16:44 ` Peter Zijlstra [this message]
2010-03-30 0:34 ` KOSAKI Motohiro
2010-03-29 22:23 ` Dave Chinner
2010-04-01 18:58 ` Maciej Rutecki
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=1269881082.12097.359.camel@laptop \
--to=peterz@infradead.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=riel@redhat.com \
/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