From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: about split the udev
Date: Sat, 24 Jan 2004 16:57:57 +0000 [thread overview]
Message-ID: <20040124165757.GA6042@vrfy.org> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8402D4EE96@PDSMSX403.ccr.corp.intel.com>
On Sun, Jan 25, 2004 at 12:06:52AM +0800, Ling, Xiaofeng wrote:
> Thank you for continuing my work. (I'm in a long vocation for two weeks)
> I'm already working on making udev to a daemon but I like your idea to let udevd
> invoke udev. This way there will be less effect to current udev.
Yes, but now we wait for the exec of udev , before we do the next.
This is much too slow if you have a lot of callouts in the rules.
I think we need something that can execute without blocking, but we
need to care that "remove" is much much faster than "add".
Greg, do we need to care about the order of execution of udev for
different device pathes?
If not, we may fork all udev's in the background, unless we have one
with the same path already running.
We may maintain the state of the fork in our sequence list and delay
all events for device pathes udev is already working on.
If we receive the SIGCHLD, then we execute the delayed one.
Hmm, if this may work?
> I've some comments about the timeout value, see below.
> > From: Kay Sievers [mailto:kay.sievers@vrfy.org]
> > So it's now possible to use the test script at any time,
> > cause it resets the daemon, if real hotplug event coming in
> > later all missing nimbers will be skipped after a timeout of
> > 10 seconds and the queued events are applied.
Yes, but we need this to follow the log while testing.
If we have a working codebase, we can set it to something useful.
> Is 10 seconds a little too longer?
> If there is only one event lost and one user have to wait 10 seconds when plugging in
> a device, is this acceptable for he/she?
> Initial, my idea is making the timeout value related with the number of lost events, so
> if happened there is one event lost, we just need to wait for 3 seconds.If two, wait for 6 seconds.
> Of couse, maybe a maximum value is also needed.
I think this is already solved.
On timeout we skip all missing events and go ahead with the next
event in the queue. So if 100 events in a row missing, there will
be one timeout only.
thanks,
Kay
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-01-24 16:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 7:53 about split the udev Ling, Xiaofeng
2004-01-12 9:36 ` Martin Waitz
2004-01-12 13:54 ` Kay Sievers
2004-01-12 16:23 ` Martin Waitz
2004-01-12 16:28 ` Robert Love
2004-01-12 17:51 ` David Zeuthen
2004-01-13 1:12 ` Greg KH
2004-01-13 1:29 ` Greg KH
2004-01-13 19:05 ` Tristan Wibberley
2004-01-13 20:36 ` Greg KH
2004-01-15 14:36 ` Ling, Xiaofeng
2004-01-15 21:45 ` Greg KH
2004-01-21 13:38 ` Kay Sievers
2004-01-22 0:27 ` Kay Sievers
2004-01-22 1:08 ` Kay Sievers
2004-01-22 23:01 ` Kay Sievers
2004-01-23 0:34 ` Greg KH
2004-01-23 1:00 ` Kay Sievers
2004-01-23 3:37 ` Kay Sievers
2004-01-23 3:46 ` Greg KH
2004-01-23 3:58 ` Kay Sievers
2004-01-23 4:04 ` Greg KH
2004-01-24 16:06 ` Ling, Xiaofeng
2004-01-24 16:57 ` Kay Sievers [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=20040124165757.GA6042@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).