From: Jens Axboe <jens.axboe@oracle.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Kay Sievers <kay.sievers@vrfy.org>,
David Zeuthen <david@fubar.dk>,
linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] [RFC] Add support for uevents on block device idle
Date: Mon, 23 Nov 2009 14:17:54 +0000 [thread overview]
Message-ID: <20091123141754.GE8742@kernel.dk> (raw)
In-Reply-To: <20091122233749.GA9699@ucw.cz>
On Mon, Nov 23 2009, Pavel Machek wrote:
> On Wed 2009-11-18 20:07:12, Matthew Garrett 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.
>
> ...when you add overhead to every disk operation. I'd say that polling
> once in 50 seconds is preferable to that.
I have to agree, doing a mod_timer() on every single IO is going to suck
big time. I went to great lengths to avoid doing that even for timeout
detection. So that's pretty much a non-starter to begin with.
Additionally, as Bart also wrote, you are not doing this in the right
place. You want to do this post-merge, not for each incoming IO. Have
you looked at laptop mode? Looks like you are essentially re-inventing
that, but in a bad way.
--
Jens Axboe
next prev parent reply other threads:[~2009-11-23 14:17 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
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 [this message]
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=20091123141754.GE8742@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=david@fubar.dk \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@ucw.cz \
/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).