From: "Chris Friesen" <cfriesen@nortel.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
ck list <ck@vds.kolivas.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH][RSDL-mm 4/6] sched: dont renice kernel threads
Date: Fri, 16 Mar 2007 09:14:32 -0600 [thread overview]
Message-ID: <45FAB458.2080304@nortel.com> (raw)
In-Reply-To: <200703170054.08641.kernel@kolivas.org>
Con Kolivas wrote:
> The practice of renicing kernel threads to negative nice values is of
> questionable benefit at best, and at worst leads to larger latencies when
> kernel threads are busy on behalf of other tasks.
What about the priority implications of the renicing? It seems a bit
iffy letting kernel threads compete for cpu time on an equal basis with
your default shell.
Chris
next prev parent reply other threads:[~2007-03-16 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 13:54 [PATCH][RSDL-mm 4/6] sched: dont renice kernel threads Con Kolivas
2007-03-16 15:14 ` Chris Friesen [this message]
2007-03-16 21:29 ` Con Kolivas
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=45FAB458.2080304@nortel.com \
--to=cfriesen@nortel.com \
--cc=akpm@linux-foundation.org \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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