From: Jan Kara <jack@suse.cz>
To: Huang Shijie <huangsj@hygon.cn>
Cc: viro@zeniv.linux.org.uk, brauner@kernel.org, zhongyuan@hygon.cn,
fangbaoshun@hygon.cn, yingzhiwei@hygon.cn, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
yefan@hygon.cn, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] fs/drop_caches: skip filesystems without fs writeback
Date: Wed, 23 Sep 2026 13:04:26 +0200 [thread overview]
Message-ID: <eabsxquvvzvn5nmffrdlpnrgm7bmajy5we4lufiyzk3l3ixope@h63fhuf4y5dd> (raw)
In-Reply-To: <20260923070116.3226846-1-huangsj@hygon.cn>
On Wed 23-09-26 15:01:16, Huang Shijie wrote:
> Filesystems backed by the noop backing device (procfs, sysfs, kernfs,
> tmpfs, ramfs, etc.) have no fs page-cache writeback. Skip them in
> drop_pagecache_sb() instead of walking their inode lists.
>
> This also skips tmpfs/ramfs. tmpfs has clean folios which are
> zero-filled pages from reading holes, which are trivially recreatable.
>
> Suggested-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Huang Shijie <huangsj@hygon.cn>
This looks indeed nice & simple. I'm slightly wondering if there isn't some
exotic read-only fs somewhere which doesn't set sb->s_bdi but so far I'm
not aware of anything (even MTD filesystems do properly setup bdi) so feel
free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> The RFC mails:
> https://lore.kernel.org/all/arIVBpMZk5-O2AZc@infradead.org/
> ---
> fs/drop_caches.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/fs/drop_caches.c b/fs/drop_caches.c
> index 49f56a598ecb..28c5fb9c7357 100644
> --- a/fs/drop_caches.c
> +++ b/fs/drop_caches.c
> @@ -7,6 +7,7 @@
> #include <linux/kernel.h>
> #include <linux/mm.h>
> #include <linux/fs.h>
> +#include <linux/backing-dev.h>
> #include <linux/writeback.h>
> #include <linux/sysctl.h>
> #include <linux/gfp.h>
> @@ -20,6 +21,9 @@ static void drop_pagecache_sb(struct super_block *sb, void *unused)
> {
> struct inode *inode, *toput_inode = NULL;
>
> + if (sb->s_bdi == &noop_backing_dev_info)
> + return;
> +
> spin_lock(&sb->s_inode_list_lock);
> list_for_each_entry(inode, &sb->s_inodes, i_sb_list) {
> spin_lock(&inode->i_lock);
> --
> 2.53.0
>
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2026-09-23 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 7:01 Huang Shijie
2026-09-23 11:04 ` Jan Kara [this message]
2026-09-25 6:57 ` 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=eabsxquvvzvn5nmffrdlpnrgm7bmajy5we4lufiyzk3l3ixope@h63fhuf4y5dd \
--to=jack@suse.cz \
--cc=brauner@kernel.org \
--cc=fangbaoshun@hygon.cn \
--cc=hch@lst.de \
--cc=huangsj@hygon.cn \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yefan@hygon.cn \
--cc=yingzhiwei@hygon.cn \
--cc=zhongyuan@hygon.cn \
/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
all inboxes | Powered by JetHome®