From: Tristan Wibberley <spamfilter@raidersofthelostfridge.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: about split the udev
Date: Tue, 13 Jan 2004 19:05:26 +0000 [thread overview]
Message-ID: <bu1f3h$2eh$1@sea.gmane.org> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8402D4EE96@PDSMSX403.ccr.corp.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greg KH wrote:
| I am talking about udev splitting into 2 pieces:
| udev - called the same way udev is called today.
| creates a tiny message queue message based on the hotplug
| event and then exits. This can probably be done in under
| 6Kb of binary code.
| udevd - receives the udev message queue messages. Orders them
| in the proper order (based on the SEQ_NUM from the
| hotplug event), and then acts on them. Size should be
| about what we have today for the udev binary 50Kb or so.
|
| We need to do this in order to properly handle out of order hotplug
| events.
Will that solve the problem? If udevd keeps up with the messages, and
the udev that supplies the second message pre-empts the one that
provides the first, will udevd process the second message because it
doesn't know that there is an earlier one about to come in?
If udevd waits for contiguous SEQ_NUMs to ensure this doesn't happen,
then a dead/locked-up udev will freeze everything (udevd won't know
which of the events it has should wait until after the unknown one). I
think a different solution is required.
Just what, I don't know - I'm quite new here :) I'm probably way off anyway.
- --
Tristan Wibberley
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD4DBQFABEF18z3lIaW+LfIRAgKdAKDOg2XGNq7SeAEO9nc0IZednOXXjACVGMsb
4DdwePXa6NP9AvgQ3OadmA=
=u3ca
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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
next prev parent reply other threads:[~2004-01-13 19:05 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 [this message]
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
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='bu1f3h$2eh$1@sea.gmane.org' \
--to=spamfilter@raidersofthelostfridge.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).