From: Matthew Wilcox <willy@infradead.org>
To: hanqi <hanqi@vivo.com>
Cc: "陈涛涛 Taotao Chen" <chentaotao@didiglobal.com>,
"tytso@mit.edu" <tytso@mit.edu>,
"hch@infradead.org" <hch@infradead.org>,
"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>,
"brauner@kernel.org" <brauner@kernel.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
"rodrigo.vivi@intel.com" <rodrigo.vivi@intel.com>,
"tursulin@ursulin.net" <tursulin@ursulin.net>,
"airlied@gmail.com" <airlied@gmail.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chentao325@qq.com" <chentao325@qq.com>,
"frank.li@vivo.com" <frank.li@vivo.com>
Subject: Re: [PATCH v4 4/5] mm/filemap: add write_begin_get_folio() helper function
Date: Mon, 7 Jul 2025 13:26:54 +0100 [thread overview]
Message-ID: <aGu9DiKbxpkq2xlx@casper.infradead.org> (raw)
In-Reply-To: <a4cc7c59-2dfd-497e-9f20-b12ea86a1baa@vivo.com>
On Mon, Jul 07, 2025 at 07:48:34PM +0800, hanqi wrote:
> I think it might be worth considering adding an fgf_t parameter to the
> write_begin_get_folio() helper, since in some filesystems the fgp_flags
> passed to __filemap_get_folio() in write_begin are not limited to just
> FGP_WRITEBEGIN. Something like:
> struct folio *write_begin_get_folio(const struct kiocb *iocb,
> struct address_space *mapping,
> pgoff_t index, size_t len,
> fgf_t fgp_flags)
The point is to make the simple cases simple. Filesystems which need
something more complicated can do it all themselves. NAK your idea.
next prev parent reply other threads:[~2025-07-07 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 7:00 [PATCH v4 0/5] fs: refactor write_begin/write_end and add ext4 IOCB_DONTCACHE support 陈涛涛 Taotao Chen
2025-07-07 7:00 ` [PATCH v4 1/5] drm/i915: Use kernel_write() in shmem object create 陈涛涛 Taotao Chen
2025-07-07 7:00 ` [PATCH v4 2/5] drm/i915: Refactor shmem_pwrite() to use kiocb and write_iter 陈涛涛 Taotao Chen
2025-07-07 7:00 ` [PATCH v4 3/5] fs: change write_begin/write_end interface to take struct kiocb * 陈涛涛 Taotao Chen
2025-07-07 7:00 ` [PATCH v4 4/5] mm/filemap: add write_begin_get_folio() helper function 陈涛涛 Taotao Chen
2025-07-07 11:48 ` hanqi
2025-07-07 12:26 ` Matthew Wilcox [this message]
2025-07-07 14:54 ` Matthew Wilcox
2025-07-08 2:40 ` Taotao Chen
2025-07-07 7:00 ` [PATCH v4 5/5] ext4: support uncached buffered I/O 陈涛涛 Taotao Chen
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=aGu9DiKbxpkq2xlx@casper.infradead.org \
--to=willy@infradead.org \
--cc=adilger.kernel@dilger.ca \
--cc=airlied@gmail.com \
--cc=brauner@kernel.org \
--cc=chentao325@qq.com \
--cc=chentaotao@didiglobal.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank.li@vivo.com \
--cc=hanqi@vivo.com \
--cc=hch@infradead.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rodrigo.vivi@intel.com \
--cc=tursulin@ursulin.net \
--cc=tytso@mit.edu \
/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).