From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: synchronization (or lack thereof) for uevents
Date: Tue, 18 Oct 2005 01:06:40 +0000 [thread overview]
Message-ID: <20051018010640.GB2817@vrfy.org> (raw)
In-Reply-To: <C2EEB4E538D3DC48BF57F391F422779321AD2B@SRMANNING.eng.emc.com>
On Mon, Oct 17, 2005 at 11:26:21AM -0400, goggin, edward wrote:
> Is it possible to ignore a hotplug event and deal only with the associated
> uevent?
>
> It seems that the asynchronous nature of uevents, (that is, they are sent to
> a netlink
> socket as datagrams -- therefore without a reply acknowledgement), makes it
> difficult
> to reliably act upon one when it is possible that multiple, related uevents,
> which although
> being sent later, may affect the servicing of the current one.
I don't really get it. /sbin/hotplug events and netlink uevents are
carrying the same content and fired at the same time. Both have the same
SEQNUM and the same keys.
Netlink uevents are a complete replacement for /sbin/hotplug.
What would an ack for the uevent be good for. These events are sent to
the socket buffer and reliable as long as they fit into the buffer. The
current udev has a buffer of 16MB which can carry app. 50.000 events
if udevd is not reading anything.
udevd reads the events and excutes them in parallel anyway. This is
intentional and there is no need or it would make sense to serialize
events besides events for the same device or a child device still
running.
What is _exactly_ your problem?
Kay
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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-10-18 1:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 15:26 synchronization (or lack thereof) for uevents goggin, edward
2005-10-18 1:06 ` Kay Sievers [this message]
2005-10-18 1:28 ` Greg KH
2005-10-18 1:53 ` goggin, edward
2005-10-18 2:33 ` Greg KH
2005-10-18 2:42 ` goggin, edward
2005-10-18 2:49 ` goggin, edward
2005-10-18 4:36 ` Greg KH
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=20051018010640.GB2817@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).