mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Matthew Garrett <mjg59@srcf.ucam.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  changes
Date: Wed, 18 Nov 2009 22:06:33 +0100	[thread overview]
Message-ID: <ac3eb2510911181306g221e8940xfbcf8b8e7fa9a56e@mail.gmail.com> (raw)
In-Reply-To: <20091118200712.GA14026@srcf.ucam.org>

On Wed, Nov 18, 2009 at 21:07, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Wed, Nov 18, 2009 at 09:03:21PM +0100, Kay Sievers wrote:
>
>> Sure, but what's wrong with reading that file every 50 seconds? Almost
>> all boxes poll for media changes of optical drives and usb card
>> readers anyway, so it's not that we are not doing stuff like this
>> already.
>
> We poll for media because there's no event-based way of avoiding it - in
> this case there is.

That's true, but I think there is a significant difference between
polling every one or two seconds for media changes, and usually one or
two minutes for a disk idle. It's not that we poll in a rather hight
frequency, in an arbitrary interval, and check if some condition is
met.

I still don't think that we should add new event interfaces which are
single-subscriber only, and use global values for a specific user.
What if there will be another independent user for this, which might
want a different timeout? They fight over the trigger value to set in
sysfs?

>From my perspective, the once-at-timeout wakeup is more acceptable
than an in-kernel policy setting for a single-subscriber event
interface.

Thanks,
Kay

  reply	other threads:[~2009-11-18 21:06 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 14:37 Matthew Garrett
2009-11-17 15:55 ` 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 [this message]
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
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-12-11 21:20                               ` [RFC] Add support for events " Matthew Garrett
2009-11-18 22:10 ` [PATCH] [RFC] Add support for uevents " 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=ac3eb2510911181306g221e8940xfbcf8b8e7fa9a56e@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=axboe@kernel.dk \
    --cc=david@fubar.dk \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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

all inboxes | Powered by JetHome®