From: Peter Zijlstra <peterz@infradead.org>
To: Andy Lutomirski <luto@mit.edu>
Cc: Suresh Jayaraman <sjayaraman@suse.de>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: High priority threads causing severe CPU load imbalances
Date: Wed, 07 Apr 2010 09:44:21 +0200 [thread overview]
Message-ID: <1270626261.5109.538.camel@twins> (raw)
In-Reply-To: <4BBC0D1E.3030509@mit.edu>
On Wed, 2010-04-07 at 00:42 -0400, Andy Lutomirski wrote:
> That's less fair but strictly better than the current solution,
> and nothing bounces.
The fairness thing, that really matters a lot to some people.
I've had enterprise bugs filed over such behaviour as you describe.
next prev parent reply other threads:[~2010-04-07 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 13:12 High priority threads causing severe CPU load imbalances Suresh Jayaraman
2010-04-06 14:08 ` Peter Zijlstra
2010-04-06 16:35 ` Suresh Jayaraman
2010-04-08 16:15 ` Peter Zijlstra
2010-04-09 2:20 ` Masayuki Igawa
2010-04-07 4:42 ` Andy Lutomirski
2010-04-07 7:44 ` Peter Zijlstra [this message]
2010-04-07 5:46 ` Masayuki Igawa
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=1270626261.5109.538.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=mingo@elte.hu \
--cc=sjayaraman@suse.de \
/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