All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: JD <jd1008@gmail.com>
Cc: linux-kernel@vger.kernel.org, Eric Paris <eparis@redhat.com>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: udevd high cpu hogging in kernel-2.6.34   git8 to git-13
Date: Fri, 28 May 2010 07:50:45 +0200	[thread overview]
Message-ID: <4BFF59B5.70002@gmail.com> (raw)
In-Reply-To: <4BFF565C.3080108@gmail.com>

On 05/28/2010 07:36 AM, JD wrote:
> I noticed that since git8, udevd consumes from 50 to 80 percent of cpu.
> The main udevd thread is niced to -4, and 6 or more child threads are
> niced -2.
> 
> So, I backpedaled to git7, which does not have this "feature" :)

Is it this one again?
http://lkml.org/lkml/2010/5/22/150

Could you try to revert the patch?

-- 
js

  reply	other threads:[~2010-05-28  5:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28  5:36 udevd high cpu hogging in kernel-2.6.34 git8 to git-13 JD
2010-05-28  5:50 ` Jiri Slaby [this message]
     [not found]   ` <4BFF5D6C.3010207@gmail.com>
2010-05-28  6:10     ` Jiri Slaby
2010-06-17 16:21       ` JD
  -- strict thread matches above, loose matches on Subject: below --
2010-05-28  4:14 JD

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=4BFF59B5.70002@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=eparis@redhat.com \
    --cc=jd1008@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.