linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	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: Mon, 05 Jan 2009 22:18:08 +0000	[thread overview]
Message-ID: <49628720.6050101@yahoo.com> (raw)
In-Reply-To: <fa.x4ejZ7Kj7ZZRu88Sond1Cap6XxY@ifi.uio.no>

Kay Sievers wrote:
> On Mon, Jan 5, 2009 at 19:54, Jens Axboe <jens.axboe@oracle.com> wrote:
>> On Mon, Jan 05 2009, Bartlomiej Zolnierkiewicz wrote:
> 
>>> +static struct queue_sysfs_entry queue_nonrot_entry = {
>>> +     .attr = {.name = "nonrot", .mode = S_IRUGO | S_IWUSR },
>>> +     .show = queue_nonrot_show,
>>> +     .store = queue_nonrot_store,
>>> +};
>>> +
>> Lets please use a better name for export reasons, non-rotational is a
>> lot better. Nobody will know what nonrot means :-)
> 
> What's that negation good for? Can't we just have "rotational", like
> we have "removable" and not "non-removable"? :)

How about cheapseek? fastrandom? flash? ssd? However the internal flag 
is called QUEUE_FLAG_NONROT so it kind of makes sense just to leave it 
as nonrot...

       reply	other threads:[~2009-01-05 22:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2009-01-06  1:25       ` [PATCH] block: export SSD/non-rotational queue flag through sysfs Stefan Richter
2009-01-06 19:46       ` Hugh Dickins
2009-01-05 18:52 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
2009-01-05 18:58 ` Alan Cox

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=49628720.6050101@yahoo.com \
    --to=sitsofe@yahoo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-ide@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).