From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 4/4] nvme: support ranged discard requests
Date: Wed, 8 Feb 2017 14:36:32 +0100 [thread overview]
Message-ID: <20170208133632.GA13064@lst.de> (raw)
In-Reply-To: <CANvN+ekrmaCZaYt02wX1DRz4+hTLicjyP-tYDTTcKsWe2Lo5MQ@mail.gmail.com>
On Wed, Feb 08, 2017@01:32:22PM +0000, Andrey Kuzmin wrote:
> On Wed, Feb 8, 2017, 16:14 Christoph Hellwig <hch@lst.de> wrote:
>
> > NVMe supports up to 255 ranges per DSM command,
>
>
> 256 per spec, with number of ranges being zero-based.
You're right. I'll do another round of the patch. That beeing
said in my tests I never even managed to get three-digit ranges
anyway with any workload.
next prev parent reply other threads:[~2017-02-08 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 13:13 support for multi-range discard requests V2 Christoph Hellwig
2017-02-08 13:13 ` [PATCH 1/4] block: move req_set_nomerge to blk.h Christoph Hellwig
2017-02-08 13:13 ` [PATCH 2/4] block: enumify ELEVATOR_*_MERGE Christoph Hellwig
2017-02-08 13:13 ` [PATCH 3/4] block: optionally merge discontiguous discard bios into a single request Christoph Hellwig
2017-02-08 13:13 ` [PATCH 4/4] nvme: support ranged discard requests Christoph Hellwig
[not found] ` <CANvN+ekrmaCZaYt02wX1DRz4+hTLicjyP-tYDTTcKsWe2Lo5MQ@mail.gmail.com>
2017-02-08 13:36 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-08 13:46 support for multi-range discard requests V3 Christoph Hellwig
2017-02-08 13:46 ` [PATCH 4/4] nvme: support ranged discard requests Christoph Hellwig
2017-02-15 10:45 ` Sagi Grimberg
2017-02-07 16:46 support for multi-range " Christoph Hellwig
2017-02-07 16:46 ` [PATCH 4/4] nvme: support ranged " Christoph Hellwig
2017-02-07 18:34 ` Keith Busch
2017-02-07 19:34 ` Christoph Hellwig
2017-02-15 10:42 ` Sagi Grimberg
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=20170208133632.GA13064@lst.de \
--to=hch@lst.de \
/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