From: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: [ANNOUNCE] udev 0.1 release
Date: Fri, 11 Apr 2003 22:27:19 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105010011402733@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105003172531462@msgid-missing>
> From: Greg KH [mailto:greg@kroah.com]
>
> But I can do a lot to prevent losses. A lot of people around here point
> to the old way PTX used to regenerate the device naming database on the
> fly. We could do that by periodically scanning sysfs to make sure we
> are keeping /dev in sync with what the system has physically present.
> That's one way, I'm sure there are others.
This might be a tad over-simplification, but sysfs knows by heart when
anything
is modified, because it goes through it's interface. If we only care about,
for example, devices, we could hook up into device_create() [was this the
name?];
line up in a queue all the devices for which an plug/unplug event hasn't
been
delivered to user space and create symlinks in /sysfs/hotplug-events/.
Each entry in there is a symlink to the new device directory, named with an
increasing integer for easy serialization. When the event is fully
processed,
remove the entry from user space.
To avoid having to scan huge directories, it could be moved to have a single
file, event. When present, it means there are events available. It
represents
the head of the in-kernel event queue. Read it [or read the symlink] for
getting
the event information. If you remove it, that means the event is delivered.
If there is an event in the queue, the file is created again for that event.
Enhance it by creating another file for out-of-band events if needed ...
Iñaky Pérez-González -- Not speaking for Intel -- all opinions are my own
(and my fault)
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
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:[~2003-04-11 22:27 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 3:24 [ANNOUNCE] udev 0.1 release Greg KH
2003-04-11 6:37 ` Oliver Neukum
2003-04-11 17:10 ` Jeremy Jackson
2003-04-11 17:18 ` Justin Cormack
2003-04-11 17:20 ` Greg KH
2003-04-11 17:21 ` Greg KH
2003-04-11 17:46 ` John Bradford
2003-04-11 18:02 ` Roman Zippel
2003-04-11 18:12 ` Oliver Neukum
2003-04-11 18:12 ` Greg KH
2003-04-11 18:23 ` Antonio Vargas
2003-04-11 18:30 ` Oliver Neukum
2003-04-11 18:31 ` Kevin P. Fleming
2003-04-11 18:52 ` Greg KH
2003-04-11 19:00 ` Oliver Neukum
2003-04-11 19:07 ` Greg KH
2003-04-11 19:09 ` Mike Dresser
2003-04-11 19:28 ` Joel Becker
2003-04-11 19:29 ` Havoc Pennington
2003-04-11 19:31 ` Oliver Neukum
2003-04-11 19:38 ` Kevin P. Fleming
2003-04-11 19:54 ` Richard B. Johnson
2003-04-11 19:58 ` Greg KH
2003-04-11 19:59 ` Mike Dresser
2003-04-11 20:09 ` Nick Craig-Wood
2003-04-11 20:10 ` Greg KH
2003-04-11 20:16 ` John Bradford
2003-04-11 20:16 ` Mike Dresser
2003-04-11 20:23 ` Chris Hanson
2003-04-11 20:29 ` Steven Dake
2003-04-11 20:32 ` Mike Dresser
2003-04-11 20:39 ` Richard B. Johnson
2003-04-11 20:42 ` Perez-Gonzalez, Inaky
2003-04-11 20:43 ` Greg KH
2003-04-11 20:47 ` Richard B. Johnson
2003-04-11 20:48 ` David Lang
2003-04-11 20:56 ` Oliver Neukum
2003-04-11 20:59 ` Greg KH
2003-04-11 21:03 ` Oliver Neukum
2003-04-11 21:28 ` Martin Mares
2003-04-11 21:52 ` Jason Riedy
2003-04-11 22:00 ` Alex Bligh - linux-kernel
2003-04-11 22:03 ` Alex Bligh - linux-kernel
2003-04-11 22:09 ` Andrew Morton
2003-04-11 22:19 ` Tim Hockin
2003-04-11 22:27 ` Perez-Gonzalez, Inaky [this message]
2003-04-11 22:30 ` Steven Dake
2003-04-11 22:32 ` Steven Dake
2003-04-11 22:36 ` Perez-Gonzalez, Inaky
2003-04-11 22:38 ` Lars Marowsky-Bree
2003-04-11 22:41 ` David Lang
2003-04-11 22:42 ` Perez-Gonzalez, Inaky
2003-04-11 22:43 ` Steven Dake
2003-04-11 22:47 ` Andrew Morton
2003-04-11 22:51 ` Greg KH
2003-04-11 22:53 ` Jason Riedy
2003-04-11 22:53 ` Greg KH
2003-04-11 22:56 ` Greg KH
2003-04-11 22:58 ` Greg KH
2003-04-11 22:59 ` Perez-Gonzalez, Inaky
2003-04-11 23:01 ` Greg KH
2003-04-11 23:03 ` Greg KH
2003-04-11 23:23 ` Andrew Morton
2003-04-11 23:25 ` Joel Becker
2003-04-11 23:25 ` Jason Riedy
2003-04-11 23:26 ` Joel Becker
2003-04-11 23:27 ` Steven Dake
2003-04-11 23:31 ` Steven Dake
2003-04-11 23:32 ` Greg KH
2003-04-11 23:32 ` Steven Dake
2003-04-11 23:35 ` Greg KH
2003-04-11 23:37 ` Steven Dake
2003-04-11 23:37 ` Greg KH
2003-04-11 23:39 ` Steven Dake
2003-04-11 23:45 ` Greg KH
2003-04-12 0:04 ` Joel Becker
2003-04-12 0:11 ` Greg KH
2003-04-12 0:19 ` Joel Becker
2003-04-12 4:20 ` Greg KH
2003-04-12 6:45 ` Lars Marowsky-Bree
2003-04-12 7:49 ` Oliver Neukum
2003-04-12 7:53 ` Oliver Neukum
2003-04-12 8:04 ` Oliver Neukum
2003-04-12 8:07 ` Greg KH
2003-04-12 12:18 ` Arnd Bergmann
2003-04-12 14:45 ` Alan Cox
2003-04-12 23:27 ` Havoc Pennington
2003-04-19 4:16 ` David Brownell
2003-04-19 4:39 ` David Brownell
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=marc-linux-hotplug-105010011402733@msgid-missing \
--to=inaky.perez-gonzalez@intel.com \
--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).