From: "hch@infradead.org" <hch@infradead.org>
To: "陈涛涛 Taotao Chen" <chentaotao@didiglobal.com>
Cc: "tytso@mit.edu" <tytso@mit.edu>,
"hch@infradead.org" <hch@infradead.org>,
"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>,
"willy@infradead.org" <willy@infradead.org>,
"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>
Subject: Re: [PATCH v2 0/5] fs: refactor write_begin/write_end and add ext4 IOCB_DONTCACHE support
Date: Tue, 24 Jun 2025 23:56:27 -0700 [thread overview]
Message-ID: <aFudm1ndfN-kTSOx@infradead.org> (raw)
In-Reply-To: <20250624121149.2927-1-chentaotao@didiglobal.com>
Thanks, I really like the i915 work to stop the shmem abuse.
I still hate it that we just change the write_begin/end ops while still
in the address_space ops vs passing explicit callbacks, because that
means we'll some other version of that abuse back sooner or later :(
prev parent reply other threads:[~2025-06-25 6:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 12:11 [PATCH v2 0/5] fs: refactor write_begin/write_end and add ext4 IOCB_DONTCACHE support 陈涛涛 Taotao Chen
2025-06-24 12:12 ` [PATCH v2 1/5] drm/i915: Use kernel_write() in shmem object create 陈涛涛 Taotao Chen
2025-06-24 12:23 ` Matthew Wilcox
2025-06-25 10:41 ` Chentaotao
2025-06-24 12:12 ` [PATCH v2 2/5] drm/i915: Refactor shmem_pwrite() to use kiocb and write_iter 陈涛涛 Taotao Chen
2025-06-24 12:12 ` [PATCH v2 3/5] fs: change write_begin/write_end interface to take struct kiocb * 陈涛涛 Taotao Chen
2025-06-24 12:51 ` Matthew Wilcox
2025-06-25 8:04 ` Christian Brauner
2025-06-27 2:40 ` Chen Taotao
2025-06-24 12:12 ` [PATCH v2 4/5] ext4: handle IOCB_DONTCACHE in buffered write path 陈涛涛 Taotao Chen
2025-06-25 14:35 ` Theodore Ts'o
2025-06-24 12:12 ` [PATCH v2 5/5] ext4: declare support for FOP_DONTCACHE 陈涛涛 Taotao Chen
2025-06-24 12:53 ` Matthew Wilcox
2025-06-25 10:46 ` Chen Taotao
2025-06-25 14:36 ` Theodore Ts'o
2025-06-24 12:54 ` [PATCH v2 0/5] fs: refactor write_begin/write_end and add ext4 IOCB_DONTCACHE support Matthew Wilcox
2025-06-24 19:25 ` ✗ LGCI.VerificationFailed: failure for " Patchwork
2025-06-25 6:56 ` hch [this message]
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=aFudm1ndfN-kTSOx@infradead.org \
--to=hch@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=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 \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.