From: Miklos Szeredi <miklos@szeredi.hu>
To: yangyun <yangyun50@huawei.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
lixiaokeng@huawei.com
Subject: Re: [PATCH] fuse: add fast path for fuse_range_is_writeback
Date: Thu, 22 Aug 2024 15:42:24 +0200 [thread overview]
Message-ID: <CAJfpegvpHb1s4eByjwKT6tEy+E8ToNXyke12=5zz3WdV_PDcrQ@mail.gmail.com> (raw)
In-Reply-To: <20240814093600.216757-1-yangyun50@huawei.com>
On Wed, 14 Aug 2024 at 11:36, yangyun <yangyun50@huawei.com> wrote:
>
> In some cases, the fi->writepages may be empty. And there is no need
> to check fi->writepages with spin_lock, which may have an impact on
> performance due to lock contention. For example, in scenarios where
> multiple readers read the same file without any writers, or where
> the page cache is not enabled.
>
> Also remove the outdated comment since commit 6b2fb79963fb ("fuse:
> optimize writepages search") has optimize the situation by replacing
> list with rb-tree.
Thanks, applied.
Miklos
prev parent reply other threads:[~2024-08-22 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 9:36 [PATCH] fuse: add fast path for fuse_range_is_writeback yangyun
2024-08-14 9:56 ` Jingbo Xu
2024-08-23 6:19 ` yangyun
2024-08-28 11:37 ` Jingbo Xu
2024-08-22 13:42 ` Miklos Szeredi [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='CAJfpegvpHb1s4eByjwKT6tEy+E8ToNXyke12=5zz3WdV_PDcrQ@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixiaokeng@huawei.com \
--cc=yangyun50@huawei.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;
as well as URLs for NNTP newsgroup(s).