From: Frank Mayhar <fmayhar@google.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: 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 10:17:10 -0700 [thread overview]
Message-ID: <1394817430.31499.216.camel@bobble.lax.corp.google.com> (raw)
In-Reply-To: <yq1d2hq27jk.fsf@sermon.lab.mkp.net>
On Wed, 2014-03-12 at 21:47 -0400, Martin K. Petersen wrote:
> I'm no big fan of dropping information.
>
> My original intent with the discard granularity and alignment was to
> allow filesystems to use them to influence block allocation and layout.
> Not to affect how we issue commands at runtime.
>
> Since a storage device is free to ignore all or parts of any discard
> request I'd consider it somewhat broken if it actually complained.
> Especially so since the relevant knobs in the standard that we key off
> of are performance recommendations and not requirements that commands
> must adhere to.
Well, in this particular case the driver is filling in the relevant
information (alignment and granularity) and then complaining later that
that information has been ignored. As I intimated earlier, it seems a
little odd to allow the driver to specify the information, only to
ignore it completely when it's time to actually use it.
Further, in my opinion this is less "dropping information" than it is
keeping information that would be dropped by the driver itself; were it
not for this adjustment, the driver would get the request, complain, and
drop it completely. This way, as much of the request as possible is
preserved while still honoring the constraints given by the driver.
--
Frank Mayhar
310-460-4042
next prev parent reply other threads:[~2014-03-14 17:17 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 [this message]
2014-03-14 20:26 ` Martin K. Petersen
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=1394817430.31499.216.camel@bobble.lax.corp.google.com \
--to=fmayhar@google.com \
--cc=axboe@kernel.dk \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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®