From: Christoph Hellwig <hch@infradead.org>
To: Zhenxian Ma <mzx199711@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@infradead.org>,
linux-block@vger.kernel.org,
Zhenxian Ma <mazhenxian@xiaohongshu.com>
Subject: Re: [PATCH v2 1/2] block: skip redundant flush for O_DSYNC direct writes
Date: Mon, 17 Aug 2026 02:19:42 -0700 [thread overview]
Message-ID: <aoLSLvofsmvlXi39@infradead.org> (raw)
In-Reply-To: <f847707d772a9225460406b5aecba030d7209b05.1786782832.git.mzx199711@gmail.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-08-17 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 13:03 [PATCH] block: skip redundant flush for O_DSYNC direct writes Zhenxian Ma
2026-08-12 16:42 ` Christoph Hellwig
2026-08-13 7:35 ` 马振先
2026-08-14 6:32 ` Christoph Hellwig
2026-08-15 9:06 ` [PATCH v2 0/2] block: avoid redundant flushes " Zhenxian Ma
2026-08-15 9:06 ` [PATCH v2 1/2] block: skip redundant flush " Zhenxian Ma
2026-08-17 9:19 ` Christoph Hellwig [this message]
2026-08-15 12:02 ` [PATCH v2 2/2] block: only use REQ_FUA for direct writes if the device supports it Zhenxian Ma
2026-08-17 9:21 ` 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=aoLSLvofsmvlXi39@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=mazhenxian@xiaohongshu.com \
--cc=mzx199711@gmail.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