From: kbusch@kernel.org (Keith Busch)
Subject: [PATCH 3/3] nvme: add proper write zeroes setup for the multipath device
Date: Tue, 12 Mar 2019 09:59:56 -0600 [thread overview]
Message-ID: <20190312155955.GC12696@localhost.localdomain> (raw)
In-Reply-To: <20190312152453.9550-4-hch@lst.de>
On Tue, Mar 12, 2019@04:24:53PM +0100, Christoph Hellwig wrote:
> Add a gendisk argument to nvme_config_write_zeroes so that the call to
> nvme_update_disk_info for the multipath device node updates the
> proper request_queue.
Looks good.
Reviewed-by: Keith Busch <keith.busch at intel.com>
next prev parent reply other threads:[~2019-03-12 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 15:24 fix discard and write zeroes configureation for multipath devices Christoph Hellwig
2019-03-12 15:24 ` [PATCH 1/3] nvme: remove nvme_ns_config_oncs Christoph Hellwig
2019-03-12 15:59 ` Keith Busch
2019-03-12 22:25 ` Sagi Grimberg
2019-03-12 15:24 ` [PATCH 2/3] nvme: add proper discard setup for the multipath device Christoph Hellwig
2019-03-12 15:59 ` Keith Busch
2019-03-12 22:25 ` Sagi Grimberg
2019-03-12 15:24 ` [PATCH 3/3] nvme: add proper write zeroes " Christoph Hellwig
2019-03-12 15:59 ` Keith Busch [this message]
2019-03-12 22:25 ` Sagi Grimberg
2019-03-12 16:08 ` fix discard and write zeroes configureation for multipath devices Max Gurtovoy
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=20190312155955.GC12696@localhost.localdomain \
--to=kbusch@kernel.org \
/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