From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: David Zeuthen <david@fubar.dk>,
linux-kernel@vger.kernel.org, axboe@kernel.dk,
linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] [RFC] Add support for uevents on block device idle
Date: Thu, 19 Nov 2009 14:48:53 +0000 [thread overview]
Message-ID: <20091119144853.GA1398@srcf.ucam.org> (raw)
In-Reply-To: <ac3eb2510911190634m20947c86w78340d22eff290ca@mail.gmail.com>
On Thu, Nov 19, 2009 at 03:34:53PM +0100, Kay Sievers wrote:
> Single-subscriber event interfaces are usually a no-go for generic
> infrastructure like this. We still have the unmodified HAL running
> until it is dead, and this works only because there are no such
> awkward interfaces. In a few years we will probably have diskfoo
> replacing dk-disks, and then ... :)
If you've got any ideas for what a multi-subscriber interface would look
like, I'm happy look at it. I don't think there's an especially
compelling use-case for one right now so I'm not enthusiastic about the
additional complexity that'd be required, but as long as there's basic
agreement that it's not practical to do this in userspace then we're at
least on the same page.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-11-19 14:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 14:37 [PATCH] [RFC] Add support for uevents on block device idle changes Matthew Garrett
2009-11-17 15:55 ` [PATCH] [RFC] Add support for uevents on block device idle Kay Sievers
2009-11-17 16:09 ` David Zeuthen
2009-11-17 18:57 ` Matthew Garrett
2009-11-18 19:30 ` Kay Sievers
2009-11-18 19:40 ` Matthew Garrett
2009-11-18 19:47 ` Kay Sievers
2009-11-18 19:53 ` Matthew Garrett
2009-11-18 20:03 ` Kay Sievers
2009-11-18 20:07 ` Matthew Garrett
2009-11-18 21:06 ` Kay Sievers
2009-11-18 21:29 ` Kay Sievers
2009-11-18 21:35 ` Matthew Garrett
2009-11-18 21:39 ` Kay Sievers
2009-11-18 21:45 ` Matthew Garrett
2009-11-18 21:33 ` Matthew Garrett
2009-11-18 21:40 ` Kay Sievers
2009-11-19 11:09 ` Kay Sievers
2009-11-19 13:01 ` Matthew Garrett
2009-11-19 13:29 ` Kay Sievers
2009-11-19 14:16 ` Matthew Garrett
2009-11-19 14:25 ` Kay Sievers
2009-11-19 14:30 ` Matthew Garrett
2009-11-19 14:34 ` Kay Sievers
2009-11-19 14:48 ` Matthew Garrett [this message]
2009-11-19 15:00 ` Kay Sievers
2009-11-20 20:29 ` Matthew Garrett
2009-11-22 23:37 ` Pavel Machek
2009-11-23 14:12 ` Matthew Garrett
2009-11-23 14:17 ` Jens Axboe
2009-11-23 14:25 ` Matthew Garrett
2009-11-23 14:31 ` Jens Axboe
2009-11-23 14:42 ` Matthew Garrett
2009-11-23 19:50 ` Jens Axboe
2009-11-23 19:54 ` Matthew Garrett
2009-11-18 22:10 ` [PATCH] [RFC] Add support for uevents on block device idle changes Bartlomiej Zolnierkiewicz
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=20091119144853.GA1398@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=axboe@kernel.dk \
--cc=david@fubar.dk \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@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).