From: Oliver Neukum <oliver@neukum.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Delayed hotplug events
Date: Fri, 18 Jun 2004 11:28:49 +0000 [thread overview]
Message-ID: <200406181328.56877.oliver@neukum.org> (raw)
In-Reply-To: <40D17ECC.20501@suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> > No, I would consider that redundant. If you let events queue up until
> > a counter reaches zero, you can guarantee that there's time to generate
> > all files being refered to in the event. There's no need to export it.
> >
> Hmm. I see. But isn't this approach conceptually identical to my patch?
> I mean, you're blocking events until a semaphore is set, whereas I'm
> dropping events during the critical section and generate them again. No
> big change.
Conceptually it makes no difference. But queueing events can be
encapsulated at the point the tasks are actually spawned. I don't see
the possibilty if you have to regenerate events.
I may, however, be wrong.
> And it doesn't change the main issue, which is that the behaviour of the
> hotplug subsystem is changed (i.e. the time when events are sent).
> Adding just another attribute doesn't change it, as it's up to the
> drivers to generate sysfs attributes.
No. An additional attribute is visible. Waiting is not. Assuming that the
attribute files are not there as the event is evaluated is _clearly_ wrong.
If you delay the events full compatibility is kept.
Waiting doesn't change anything fundamentally. It just makes sure that
the hotplug subsystem always behaves in a way it may behave currently.
Regards
Oliver
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA0tH1buJ1a+1Sn8oRArNFAKDkTCKOxrcsheTmWVpcRyFhDY+H+QCdEt+O
7sBLA1aO2QAsmfIbA3OAQJ8=LeBA
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
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-06-18 11:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 11:21 Delayed hotplug events Hannes Reinecke
2004-06-17 18:09 ` Greg KH
2004-06-17 19:56 ` Oliver Neukum
2004-06-17 20:22 ` linas
2004-06-17 23:29 ` Patrick Mansfield
2004-06-17 23:39 ` Greg KH
2004-06-17 23:40 ` Greg KH
2004-06-17 23:57 ` Greg KH
2004-06-18 7:44 ` Oliver Neukum
2004-06-18 8:12 ` Hannes Reinecke
2004-06-18 8:47 ` Oliver Neukum
2004-06-18 9:32 ` Hannes Reinecke
2004-06-18 11:28 ` Oliver Neukum [this message]
2004-06-19 0:07 ` Greg KH
2004-06-19 8:16 ` Oliver Neukum
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=200406181328.56877.oliver@neukum.org \
--to=oliver@neukum.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).