From: Keith Busch <keith.busch@intel.com>
To: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
Cc: axboe@fb.com, martin.petersen@oracle.com,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
Chaitanya Kulkarni <chaitanya.kulkarni@hgst.com>
Subject: Re: [PATCH v2 2/5] block: add support for REQ_OP_WRITE_ZEROES
Date: Fri, 18 Nov 2016 10:41:29 -0500 [thread overview]
Message-ID: <20161118154129.GE12377@localhost.localdomain> (raw)
In-Reply-To: <1479421031-6060-1-git-send-email-ckulkarnilinux@gmail.com>
On Thu, Nov 17, 2016 at 02:17:11PM -0800, Chaitanya Kulkarni wrote:
> From: Chaitanya Kulkarni <chaitanya.kulkarni@hgst.com>
>
> This adds a new block layer operation to zero out a range of
> LBAs. This allows to implement zeroing for devices that don't use
> either discard with a predictable zero pattern or WRITE SAME of zeroes.
> The prominent example of that is NVMe with the Write Zeroes command,
> but in the future this should also help with improving the way
> zeroing discards work.
>
> Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni@hgst.com>
> ---
I think we also to assign queue_limits for stacked devices in
blk_stack_limits. Otherwise, looks good.
next prev parent reply other threads:[~2016-11-18 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 22:17 [PATCH v2 2/5] block: add support for REQ_OP_WRITE_ZEROES Chaitanya Kulkarni
2016-11-18 2:22 ` Martin K. Petersen
2016-11-18 7:46 ` Christoph Hellwig
2016-11-18 8:25 ` chaitany kulkarni
2016-11-18 15:41 ` Keith Busch [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-30 20:28 [PATCH V2 1/5] block: add async variant of blkdev_issue_zeroout Chaitanya Kulkarni
2016-11-30 20:28 ` [PATCH V2 2/5] block: add support for REQ_OP_WRITE_ZEROES Chaitanya Kulkarni
2016-12-01 10:00 ` Christoph Hellwig
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=20161118154129.GE12377@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=axboe@fb.com \
--cc=chaitanya.kulkarni@hgst.com \
--cc=ckulkarnilinux@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).