From: Guixin Liu <kanie@linux.alibaba.com>
To: Christoph Hellwig <hch@lst.de>
Cc: sagi@grimberg.me, kch@nvidia.com, linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2] nvmet: avoid unnecessary fsync and flush bio
Date: Wed, 27 Jul 2022 16:03:43 +0800 [thread overview]
Message-ID: <5a28ee53-0bed-11ab-6817-e60f2ca70ed9@linux.alibaba.com> (raw)
In-Reply-To: <20220726113333.GA2867@lst.de>
在 2022/7/26 19:33, Christoph Hellwig 写道:
> On Mon, Jul 25, 2022 at 02:28:18PM +0800, Guixin Liu wrote:
>> u16 nvmet_file_flush(struct nvmet_req *req)
>> {
>> - return errno_to_nvme_status(req, vfs_fsync(req->ns->file, 1));
>> + if (req->ns->buffered_io)
>> + return errno_to_nvme_status(req, vfs_fsync(req->ns->file, 1));
>> + return NVME_SC_SUCCESS;
> This is broken. Even direct I/O needs an fsync to commit metadata
> changes.
Well, you are right, I will send V3 patch with remove this change.
Thanks,
Guixin Liu
next prev parent reply other threads:[~2022-07-27 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 6:28 [PATCH v2] nvmet: avoid unnecessary fsync and flush bio Guixin Liu
2022-07-26 6:17 ` Chaitanya Kulkarni
2022-07-26 11:33 ` Christoph Hellwig
2022-07-27 8:03 ` Guixin Liu [this message]
2022-07-27 8:08 ` Chaitanya Kulkarni
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=5a28ee53-0bed-11ab-6817-e60f2ca70ed9@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=hch@lst.de \
--cc=kch@nvidia.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