All of lore.kernel.org
 help / color / mirror / Atom feed
From: JD <jd1008@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: udevd high cpu hogging in kernel-2.6.34   git8 to git-13
Date: Thu, 17 Jun 2010 09:21:04 -0700	[thread overview]
Message-ID: <4C1A4B70.2010402@gmail.com> (raw)
In-Reply-To: <4BFF5E3B.5060305@gmail.com>



On 05/27/2010 11:10 PM, Jiri Slaby wrote:
> Added lkml back to CC.
>
> On 05/28/2010 08:06 AM, JD wrote:
>    
>> But here goes:
>> I have seen this behaviour in all the git releases from git8
>> to the current 2.6.34-git13
>>
>> I have some of the analysis based on strace, and kernel stack
>> trace.
>> Instead of backing out the whole code for the new udevd, perhaps
>> it (udevd) should sleep for some time before polling the same fd
>> again.
>>      
> So if you see in the strace output the poll to return immediately with
> out fd being an anon_inode (check /proc/pid_of_udev/fd/), it is the
> issue. AFAIK, it was not fixed upstream yet.
>
> So could you try to revert a7cf4145b?
>
>    
As promised, I tested the patch submitted by Eric Paris
(See http://marc.info/?l=linux-kernel&m=127479018618584&w=2).
I patched kernel-2.6.34-git13 with it, without reverting a7cf4145b.
The thing is it works and works extremely well.
The behaviour is back to what it used to be: Only 3 udevd
threads, as in before git8, and they do not consume any
cpu bandwidth that I can see. It is well below the threshold
of 1% .

Also, it seems that it has been picked up by upstream. Compiled
and booted 2.6.34-git16 and all is well.


  reply	other threads:[~2010-06-17 16:21 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
     [not found]   ` <4BFF5D6C.3010207@gmail.com>
2010-05-28  6:10     ` Jiri Slaby
2010-06-17 16:21       ` JD [this message]
  -- 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=4C1A4B70.2010402@gmail.com \
    --to=jd1008@gmail.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 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.