From: Jiri Slaby <jirislaby@gmail.com>
To: JD <jd1008@gmail.com>
Cc: Eric Paris <eparis@redhat.com>, Al Viro <viro@zeniv.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: udevd high cpu hogging in kernel-2.6.34 git8 to git-13
Date: Fri, 28 May 2010 08:10:03 +0200 [thread overview]
Message-ID: <4BFF5E3B.5060305@gmail.com> (raw)
In-Reply-To: <4BFF5D6C.3010207@gmail.com>
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?
--
js
next prev parent reply other threads:[~2010-05-28 6:10 UTC|newest]
Thread overview: 4+ 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 [this message]
2010-06-17 16:21 ` 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=4BFF5E3B.5060305@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).