From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: I'm lost: the udev workflow
Date: Fri, 24 Jun 2005 10:23:54 +0000 [thread overview]
Message-ID: <20050624102354.GA21988@vrfy.org> (raw)
In-Reply-To: <200506240403.35408.ml@gioelebarabucci.com>
On Fri, Jun 24, 2005 at 04:03:35AM +0200, Gioele Barabucci wrote:
> Now I'm lost. I'm no longer sure about the way udev, the kernel and other
> device management apps work together.
>
> I was thinking that the workflow was:
>
> * something happens to a device (add, remove, power state change)
> * the kernel calls /sbin/hotplug
> * udev is called and does its work (modprobe, rmmod, device node
> creation/deletion)
> * all the "interested listeners" (like HAL) are called and are told of what
> has changed.
>
> Now I read of netlink, listening daemons, KEYs... Can someone draft a quick
> sketch of how kernel hotplug is going to work with the next udev releases?
udevd already keeps track of the event management as it does today. The
only difference is that it receives the kernel-events directly from a
netlink-socket instead of letting the kernel fork a notification process
that feeds udevd.
This saves us one process per event, makes the event-ordering
predictable and does not kill the box if thousends of events happen in
parallel (we have such boxes here and you can't control the kernel
forked events which are causing OOM in that case).
Kay
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
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:[~2005-06-24 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 2:03 I'm lost: the udev workflow Gioele Barabucci
2005-06-24 10:23 ` Kay Sievers [this message]
2005-06-24 11:36 ` Gioele Barabucci
2005-06-24 11:50 ` 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=20050624102354.GA21988@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).