mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>, Jens Axboe <axboe@kernel.dk>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	martin.petersen@oracle.com
Subject: Re: [RFC PATCH] block: Change default IO scheduler to deadline except SATA
Date: Wed, 11 Apr 2012 12:25:15 -0400	[thread overview]
Message-ID: <yq14nsqck2c.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <CAMM=eLf5qi_PL8vFh_b5V_nq_mxg0CN0asE8E9XYJn48J4mdPA@mail.gmail.com> (Mike Snitzer's message of "Tue, 10 Apr 2012 12:13:07 -0400")

>>>>> "Mike" == Mike Snitzer <snitzer@redhat.com> writes:

Mike> I'm not aware of any discrete attribute (comparable to
Mike> 'rotational' flag) that SCSI devices will advertise that indicates
Mike> "I'm a raid array".

Sadly, no.


Mike> That said, we can have a _very_ good hint that a SCSI device is a
Mike> raid array if:

Mike> 1) optimal_io_size is not zero, minimum_io_size is not equal to
Mike> optimal_io_size, and optimal_io_size is a multiple of
Mike> minimum_io_size

Unfortunately there are still a lot of arrays out there that don't
export the relevant VPDs.

I know there's a lot of resistance to doing stuff in the kernel that can
be done in udev. But with my distro hat on we update the kernel much,
much more frequently than we update udev rules. For a multitude of
reasons.

Also, when it comes to disk arrays we already have a significant portion
of them hardwired in the kernel anyway (quirks, LUN discovery, device
handlers). So I'd personally be fine with having a BLIST_ARRAY flag that
we could trigger off of.

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2012-04-11 16:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 13:37 Vivek Goyal
2012-04-10 13:56 ` Jens Axboe
2012-04-10 14:21   ` Vivek Goyal
2012-04-10 15:10     ` Vivek Goyal
2012-04-10 16:13       ` Mike Snitzer
2012-04-10 17:28         ` Vivek Goyal
2012-04-10 17:40           ` Mike Snitzer
2012-04-10 18:36         ` Jens Axboe
2012-04-11 16:25         ` Martin K. Petersen [this message]
2012-04-10 18:41       ` Jens Axboe
2012-04-10 18:53         ` Vivek Goyal
2012-04-10 18:56           ` Jens Axboe
2012-04-10 19:11             ` Vivek Goyal
2012-04-10 19:19               ` Jens Axboe
2012-04-10 19:43                 ` Mike Snitzer
2012-04-10 19:55                   ` Jens Axboe
2012-04-10 20:12                     ` Mike Snitzer
2012-04-10 17:44 Xose Vazquez Perez

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=yq14nsqck2c.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snitzer@redhat.com \
    --cc=vgoyal@redhat.com \
    /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

Powered by JetHome