From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH 1/2] udevd: respect the value of TIMEOUT in uevents
Date: Tue, 26 May 2009 16:55:50 +0000 [thread overview]
Message-ID: <4A1C1F16.7080100@tuffmail.co.uk> (raw)
In-Reply-To: <4A1BBBE6.4040202@tuffmail.co.uk>
Kay Sievers wrote:
> On Tue, May 26, 2009 at 12:19, Alan Jenkins <alan-jenkins@tuffmail.co.uk> wrote:
>
>
>> Don't apply patch 2 then :-).
>>
>
> No worry, we can not be that fast here. :) We need to get numbers first.
>
> Threads don't come for free, they make udev much less reliable and
> harder to debug, compared to the current model. When all events share
> the same address space, and the memory for the events gets reused for
> forever, a simple bug will likely bring down the entire service,
> unlike today where an event process may crash, but the event
> management daemon will survive. Actually, I don't remember that the
> main udev ever crashed, and that will definitely change with the
> threads. :)
>
> I'm not against a threaded udevd, but we should have a good reason to
> do it that way. We also need to get numbers on bigger boxes. Udev runs
> on boxes with many thousands of events at bootup. we've seen boxes
> with 20.000+ disks, where every disk has ~10 devices in sysfs. Some of
> the SUSE customers requested to be able to run 4000+ events in
> parallel, to bring the bootup time on such boxes down to a reasonable
> time. That all works fine with today's udev and we need to be really
> careful here.
>
> Thanks,
> Kay
>
Noted and agreed. I'll work towards a complete series which can be
tested and reviewed as a whole.
Thanks
Alan
prev parent reply other threads:[~2009-05-26 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 9:52 [PATCH 1/2] udevd: respect the value of TIMEOUT in uevents Alan Jenkins
2009-05-26 10:17 ` Kay Sievers
2009-05-26 10:19 ` Alan Jenkins
2009-05-26 15:31 ` Kay Sievers
2009-05-26 16:55 ` Alan Jenkins [this message]
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=4A1C1F16.7080100@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=linux-hotplug@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 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).