From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Frank Mayhar <fmayhar@google.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Jeff Moyer <jmoyer@redhat.com>, Jens Axboe <axboe@kernel.dk>,
linux-kernel <linux-kernel@vger.kernel.org>,
Theodore Tso <tytso@google.com>
Subject: Re: [PATCH] block: Force sector and nr_sects to device alignment and granularity.
Date: Fri, 14 Mar 2014 16:26:08 -0400 [thread overview]
Message-ID: <yq1vbvgwmqn.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1394817430.31499.216.camel@bobble.lax.corp.google.com> (Frank Mayhar's message of "Fri, 14 Mar 2014 10:17:10 -0700")
>>>>> "Frank" == Frank Mayhar <fmayhar@google.com> writes:
Frank,
Frank> Well, in this particular case the driver is filling in the
Frank> relevant information (alignment and granularity) and then
Frank> complaining later that that information has been ignored. As I
Frank> intimated earlier, it seems a little odd to allow the driver to
Frank> specify the information, only to ignore it completely when it's
Frank> time to actually use it.
Which driver is this?
In T10 SBC these values are performance hints, not hard
requirements. They were never intended as such.
Frank> Further, in my opinion this is less "dropping information" than
Frank> it is keeping information that would be dropped by the driver
Frank> itself; were it not for this adjustment, the driver would get the
Frank> request, complain, and drop it completely. This way, as much of
Frank> the request as possible is preserved while still honoring the
Frank> constraints given by the driver.
The problem arises if you combine devices with different
granularity. The I/O topology code is then forced to scale the
granularity up.
If you enforce the granularity at the top of the stack it means the
device(s) with lesser granularity will lose information which would
otherwise be valuable to them.
We have previously entertained enforcing the granularity at the bottom
of the stack on a per-device basis. However, I stand by my opinion that
the device behavior is broken. I'd never let a device like that pass
qualification here...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-03-14 20:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 18:01 Frank Mayhar
2014-03-11 15:15 ` Jeff Moyer
2014-03-11 16:02 ` Frank Mayhar
2014-03-12 18:20 ` Jeff Moyer
2014-03-12 18:39 ` Frank Mayhar
2014-03-12 19:33 ` Jeff Moyer
2014-03-12 19:51 ` Frank Mayhar
2014-03-13 1:47 ` Martin K. Petersen
2014-03-14 17:17 ` Frank Mayhar
2014-03-14 20:26 ` Martin K. Petersen [this message]
2014-03-12 18:06 ` Frank Mayhar
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=yq1vbvgwmqn.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=fmayhar@google.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@google.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
all inboxes | Powered by JetHome®