mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: pavel@pavlinux.ru
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: INGO Why you remove  set_user_nice() from kernel/kthread.c
Date: Mon, 14 Sep 2009 16:05:40 +0200	[thread overview]
Message-ID: <1252937140.6500.11.camel@marge.simson.net> (raw)
In-Reply-To: <200909141742.45487.pavel@pavlinux.ru>

If you're asking Ingo a question, maybe a CC is in order.

On Mon, 2009-09-14 at 17:42 +0400, Pavel Vasilyev wrote:
> 
> Next patсh -  
> http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2F%2Fv2.6%2Fsnapshots%2Fpatch-2.6.31-git2.bz2;z=548
> 
> This patch defines the core processes that are working with nice leve equal to 
> zero , as in the BFS. :)
> 
> Why?

I did that, not Ingo, and did so because with kthreads that use
diddly-spit CPU (every one I see), it's just a waste of math.  What
kthreads are you seeing using so much CPU that their weight is a factor?
They _should_ be able to preempt and get their work done just fine
without a boost.

> VirtualBox, Vmware, QEMU, Firefox, Azureus, and many subsystems and 
> applications began working with large timeouts. In appearance similar to 
> hang.

In any case, if it's causing problems, reverting is easy enough, though
better would be to find out the why.

	-Mike



  reply	other threads:[~2009-09-14 14:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 13:42 Pavel Vasilyev
2009-09-14 14:05 ` Mike Galbraith [this message]
2009-09-14 15:12   ` Chris Friesen
2009-09-14 15:35     ` Pavel Vasilyev
2009-09-18  9:13       ` Thomas Gleixner
2009-09-14 15:45     ` Mike Galbraith
2009-09-14 16:31       ` Chris Friesen
2009-09-14 16:36         ` Mike Galbraith
2009-09-19  9:18 Pavel Vasilyev

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=1252937140.6500.11.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pavel@pavlinux.ru \
    /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

all inboxes | Powered by JetHome®