From: Mike Waychison <Michael.Waychison@Sun.COM>
To: Tim Hockin <thockin@hockin.org>
Cc: Greg KH <greg@kroah.com>, Oliver Neukum <oliver@neukum.org>,
Robert Love <rml@ximian.com>,
"Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
Andrew Morton <akpm@osdl.org>,
cw@f00f.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] kernel events layer
Date: Tue, 27 Jul 2004 14:15:20 -0400 [thread overview]
Message-ID: <41069BB8.1030405@sun.com> (raw)
In-Reply-To: <20040726204457.GA10970@hockin.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tim Hockin wrote:
> On Mon, Jul 26, 2004 at 03:03:05PM -0400, Greg KH wrote:
>
>>>On a related note, is this supposed to supersede the current hotplug
>>>mechanism?
>>
>>No, it will not. At the most, it will report the same information to
>>make it easier for userspace programs who want to get the other
>>event information, also get the hotplug stuff through the same
>>interface, reducing their complexity.
>>
>>So the existing hotplug interface is not going away at all. Do not even
>>begin to think that :)
>
>
> What about flipping it around and using either hotplug or a hotplug-like
> mechanism for these events?
>
> It solves the issue of events being dropped when there is no listening
> daemon...
>
> These are not going to be high-traffic messages, right, so the overhead is
> negligible...
>
The problem with this is that you'd lose the ability to send the
messages broadcast, whereby you may have multiple dbus's listening for
events.
- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
http://www.sun.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBBpu3dQs4kOxk3/MRAthIAJ41mD9SV3tfZosw2H26Vt4xayKP5ACbB4Eb
QQImIFvK2NXCt0B5dHPj5ps=
=1TDt
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-07-27 18:17 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 7:31 [patch] kernel events layer Perez-Gonzalez, Inaky
2004-07-26 14:50 ` Robert Love
2004-07-26 16:12 ` Greg KH
2004-07-26 18:13 ` Oliver Neukum
2004-07-26 18:15 ` Robert Love
2004-07-26 19:03 ` Greg KH
2004-07-26 20:44 ` Tim Hockin
2004-07-27 18:15 ` Mike Waychison [this message]
2004-07-27 18:35 ` Oliver Neukum
2004-07-27 18:37 ` Tim Hockin
-- strict thread matches above, loose matches on Subject: below --
2004-07-26 22:58 Perez-Gonzalez, Inaky
2004-07-27 7:08 ` Deepak Saxena
2004-07-26 6:04 Perez-Gonzalez, Inaky
2004-07-26 6:09 ` Andrew Morton
2004-07-26 23:00 ` Matt Mackall
2004-07-23 17:41 Robert Love
2004-07-23 18:25 ` Tim Hockin
2004-07-23 18:31 ` Muli Ben-Yehuda
2004-07-23 18:35 ` Robert Love
2004-07-23 21:32 ` Dan Aloni
2004-07-24 2:47 ` Robert Love
2004-07-24 4:42 ` Keith Owens
2004-07-24 5:00 ` Robert Love
2004-07-24 8:11 ` Andrew Morton
2004-07-24 5:37 ` Robert Love
2004-07-24 6:02 ` Robert Love
2004-07-24 9:43 ` Wichert Akkerman
2004-07-24 20:21 ` James Morris
2004-07-25 2:12 ` Robert Love
2004-07-24 6:53 ` Paul Jackson
2004-07-24 11:37 ` Bernd Petrovitsch
2004-07-24 3:02 ` Michael Clark
2004-07-24 3:14 ` Robert Love
2004-07-24 9:15 ` Michael Clark
2004-07-24 15:08 ` Deepak Saxena
2004-07-24 15:45 ` Robert Love
2004-07-24 17:33 ` Ryan Anderson
2004-07-24 17:46 ` Tim Hockin
2004-07-24 18:19 ` Robert Love
2004-07-25 18:11 ` Tim Hockin
2004-07-25 19:08 ` Robert Love
2004-07-27 5:09 ` Daniel Stekloff
2004-07-24 17:54 ` Deepak Saxena
2004-07-24 18:13 ` Robert Love
2004-07-26 20:08 ` Rutger Nijlunsing
2004-07-26 20:10 ` Robert Love
2004-08-09 13:29 ` Pavel Machek
2004-08-09 19:47 ` Robert Love
2004-07-24 3:03 ` Andrew Morton
2004-07-24 2:14 ` Robert Love
2004-07-24 5:15 ` Chris Wedgwood
2004-07-24 5:41 ` Robert Love
2004-07-24 5:45 ` Chris Wedgwood
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=41069BB8.1030405@sun.com \
--to=michael.waychison@sun.com \
--cc=akpm@osdl.org \
--cc=cw@f00f.org \
--cc=greg@kroah.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=rml@ximian.com \
--cc=thockin@hockin.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