public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: davidsen@posidon.tmr.com
Cc: Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] another scheduler beater
Date: Tue, 24 Apr 2007 06:36:33 +0200	[thread overview]
Message-ID: <1177389393.6299.16.camel@Homer.simpson.net> (raw)
In-Reply-To: <462D2B4E.7050009@tmr.com>

On Mon, 2007-04-23 at 17:55 -0400, Bill Davidsen wrote:

> Based on just this script as load I would say renice on X isn't a good 
> thing. Based on one small test, I would say that renice of X in 
> conjunction with heavy disk i/o and a single fast scrolling xterm (think 
> kernel compile) seems to slow the raid6 thread measurably.

Yeah, I was testing a UP kernel yesterday.  It doesn't take much renice
to severely injure the competition with them having no place else to go.
Nice -19 is definitely overkill.

	-Mike


  reply	other threads:[~2007-04-24  4:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 21:55 [RFC] another scheduler beater Bill Davidsen
2007-04-24  4:36 ` Mike Galbraith [this message]
2007-04-24  8:17 ` Ingo Molnar
2007-04-24 12:06   ` Ed Tomlinson

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=1177389393.6299.16.camel@Homer.simpson.net \
    --to=efault@gmx.de \
    --cc=davidsen@posidon.tmr.com \
    --cc=linux-kernel@vger.kernel.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