linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Grant Grundler <grundler@google.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	Greg Freemyer <greg.freemyer@gmail.com>,
	Tejun Heo <htejun@gmail.com>, Michael Tokarev <mjt@tls.msk.ru>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] block: export SSD/non-rotational queue flag through sysfs
Date: Fri, 16 Jan 2009 07:43:02 +0100	[thread overview]
Message-ID: <20090116064301.GR30821@kernel.dk> (raw)
In-Reply-To: <da824cf30901151445q6b54c0b1nbf24f03849e1a5b3@mail.gmail.com>

On Thu, Jan 15 2009, Grant Grundler wrote:
> On Thu, Jan 15, 2009 at 11:00 AM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> ...
> >> Code can test for zero/nonzero or (preferably) more fine grained.
> >> e.g. "avgreadcost > 1ms" or "avgwritecost". I'm hoping this test
> >> can be abstracted into a macro.
> >
> > Um these really have to be things we can get out of the device at boot
> > time without effort (as in part of the data the device can give in a
> > single command).  I'll be shot for increasing boot time so we can work
> > out these parameters ...
> 
> No. The whole point is we should not care what it is at boot time.  It
> should be based on recent history of what is going on.  At boot time
> we read the partition table and we superblocks to mount file systems.
> That's fine to start with. So I don't see any need to add some
> synthetic test to establish initial values.
> 
> The rest of the code should work regardless of what the values start
> out to be.  This is true for the previous proposed patch too when user
> space has to decide what the right policy is.

I absolutely hate the idea of rw cost numbers. Why? Because it's a
property that's impossible to present as a single number. It depends on
so many different things, like cache settings and access pattern. If you
just want to know the avg seek time of your device, look at the reported
RPM value. Userspace can do that, because the kernel doesn't really care
a whole lot about it to be honest.

-- 
Jens Axboe


  parent reply	other threads:[~2009-01-16  6:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 18:52 [PATCH] block: export SSD/non-rotational queue flag through sysfs Bartlomiej Zolnierkiewicz
2009-01-05 18:54 ` Jens Axboe
2009-01-05 19:02   ` Bartlomiej Zolnierkiewicz
2009-01-05 19:08     ` James Bottomley
2009-01-05 19:10       ` Jens Axboe
2009-01-05 19:08     ` Jens Axboe
2009-01-05 21:47   ` Kay Sievers
2009-01-06  7:35     ` Jens Axboe
2009-01-07 10:39       ` Michael Tokarev
2009-01-07 11:19         ` Jens Axboe
2009-01-07 15:34         ` James Bottomley
2009-01-15  5:37           ` Tejun Heo
2009-01-15 15:07             ` Greg Freemyer
2009-01-15 15:46               ` Tejun Heo
2009-01-15 16:06               ` James Bottomley
2009-01-15 18:55                 ` Grant Grundler
2009-01-15 19:00                   ` James Bottomley
2009-01-15 22:45                     ` Grant Grundler
2009-01-15 23:17                       ` James Bottomley
2009-01-15 23:50                         ` Hugh Dickins
2009-01-15 23:57                           ` Michael Tokarev
2009-01-16  0:36                           ` James Bottomley
2009-01-16  3:52                             ` Dongjun Shin
2009-01-16  6:48                               ` Jens Axboe
2009-01-16  6:48                           ` Jens Axboe
2009-02-03 12:32                             ` Pierre Ossman
2009-01-16  6:43                       ` Jens Axboe [this message]
2009-01-05 18:58 ` Alan Cox
     [not found] <fa.+H1UnEqOmFht/vMPmVy8ellbQi0@ifi.uio.no>
     [not found] ` <fa.RLz5WOGorLui5GRkc963Ww1kXqg@ifi.uio.no>
     [not found]   ` <fa.x4ejZ7Kj7ZZRu88Sond1Cap6XxY@ifi.uio.no>
2009-01-05 22:18     ` Sitsofe Wheeler
2009-01-06  1:25       ` Stefan Richter
2009-01-06 19:46       ` Hugh Dickins

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=20090116064301.GR30821@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=greg.freemyer@gmail.com \
    --cc=grundler@google.com \
    --cc=htejun@gmail.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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).