From: JD on
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" :)

Cheers,

JD

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jiri Slaby on
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jiri Slaby on
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/