From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"hch@lst.de" <hch@lst.de>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
"sagi@grimberg.me" <sagi@grimberg.me>
Subject: Re: [PATCH v3] nvmet: avoid unnecessary flush bio
Date: Thu, 4 Aug 2022 06:46:13 +0000 [thread overview]
Message-ID: <784f09f0-eca8-631e-2c30-55600893420e@nvidia.com> (raw)
In-Reply-To: <1659066785-88807-1-git-send-email-kanie@linux.alibaba.com>
On 7/28/22 20:53, Guixin Liu wrote:
> For no volatile write cache block device backend, sending flush bio is
> unnecessary, avoid to do that.
>
> Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
> ---
>
> Changes on v3:
> - Remove file backend change.
>
> Changes on v2:
> - Use bdev_write_cache instead of open code.
> - Use NVME_SC_SUCCESS instead of translation, and remove "else".
>
> Test log:
> - Add printk log at new if branch.
> - Use nvme_loop to emulate nvme device.
> - Use tcm_loop and tcmu to emulate no volatile write cache block backend
> by setting emulate_write_cache=0.
> - Send "nvme flush /dev/nvme0n1", there is a log print, and cmd return success.
> - Send "nvme set-feature /dev/nvme0n1 --namespace-id=1 --feature-id=0x84 --value=1",
> there is a log print, and cmd return success.
> - Format nvme0n1 to ext4 filesystem, then create a file, write data and save, there
> is a log print, and no error.
>
> drivers/nvme/target/io-cmd-bdev.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
Thanks for the test report, looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2022-08-04 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 3:53 [PATCH v3] nvmet: avoid unnecessary flush bio Guixin Liu
2022-08-01 8:54 ` Guixin Liu
2022-08-01 17:25 ` Christoph Hellwig
2022-08-04 6:46 ` Chaitanya Kulkarni [this message]
2022-09-05 11:02 ` 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=784f09f0-eca8-631e-2c30-55600893420e@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=kanie@linux.alibaba.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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