All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Ming Lin <mlin@kernel.org>, Mike Snitzer <snitzer@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Kent Overstreet <kent.overstreet@gmail.com>
Subject: Re: block: re-add discard_granularity and alignment checks
Date: Wed, 28 Oct 2015 09:13:59 +0900	[thread overview]
Message-ID: <56301347.9090701@kernel.dk> (raw)
In-Reply-To: <CAF1ivSapbRDuQX5iW5MyC=YWiu0poKoFhVKRcut+rLR1fsv2iQ@mail.gmail.com>

On 10/28/2015 06:23 AM, Ming Lin wrote:
> On Thu, Oct 22, 2015 at 10:03 AM, Mike Snitzer <snitzer@redhat.com> wrote:
>> On Thu, Oct 22 2015 at 12:59pm -0400,
>> Ming Lin <mlin@kernel.org> wrote:
>>
>>> From: Ming Lin <ming.l@ssi.samsung.com>
>>>
>>> In commit b49a087("block: remove split code in
>>> blkdev_issue_{discard,write_same}"), discard_granularity and alignment
>>> checks were removed. Ideally, with bio late splitting, the upper layers
>>> shouldn't need to depend on device's limits.
>>>
>>> Christoph reported a discard regression on the HGST Ultrastar SN100 NVMe
>>> device when mkfs.xfs. We have not found the root cause yet.
>>>
>>> This patch re-adds discard_granularity and alignment checks by reverting
>>> the related changes in commit b49a087. The good thing is now we can
>>> remove the 2G discard size cap and just use UINT_MAX to avoid bi_size
>>> overflow.
>>>
>>> Reviewed-by: Christoph Hellwig <hch@lst.de>
>>> Tested-by: Christoph Hellwig <hch@lst.de>
>>> Signed-off-by: Ming Lin <ming.l@ssi.samsung.com>
>>
>> Reviewed-by: Mike Snitzer <snitzer@redhat.com>
>
> Hi Jens,
>
> Would you please take this one?

I was going to add it for 4.3, but hch just pointed out that it's a 
regression in this series. I'll send it in for 4.3.

-- 
Jens Axboe


      reply	other threads:[~2015-10-28  0:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 16:59 [PATCH] block: re-add discard_granularity and alignment checks Ming Lin
2015-10-22 17:03 ` Mike Snitzer
2015-10-27 21:23   ` Ming Lin
2015-10-28  0:13     ` Jens Axboe [this message]

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=56301347.9090701@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mlin@kernel.org \
    --cc=snitzer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.