From: Andrew Morton <akpm@linux-foundation.org>
To: Jim Zhao <jimzhao.ai@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, willy@infradead.org
Subject: Re: [PATCH] mm/page-writeback: Raise wb_thresh to prevent write blocking with strictlimit
Date: Fri, 25 Oct 2024 17:02:22 -0700 [thread overview]
Message-ID: <20241025170222.0ced663e778935946ea1c9fa@linux-foundation.org> (raw)
In-Reply-To: <20241024072919.468589-1-jimzhao.ai@gmail.com>
On Thu, 24 Oct 2024 15:29:19 +0800 Jim Zhao <jimzhao.ai@gmail.com> wrote:
> > > 2. FUSE with Unstable Network Backends and Occasional Writes
> > > Not easy to reproduce, but when it occurs in this scenario,
> > > it causes the write thread to experience more pauses and longer durations.
>
> > Thanks, but it's still unclear how this impacts our users. How lenghty
> > are these pauses?
>
> The length is related to device writeback bandwidth.
> Under normal bandwidth, each pause may last around 4ms in several times as shown in the trace above(5 times).
> In extreme cases, fuse with unstable network backends,
> if pauses occur frequently and bandwidth is low, each pause can exceed 10ms, the total duration of pauses can accumulate to second.
Thanks. I'll assume that the userspace impact isn't serious to warrant
a backport into -stable kernel.
If you disagree with this, please let me know and send along additional
changelog text which helps others understand why we think our users
will significantly benefit from this change.
next prev parent reply other threads:[~2024-10-26 0:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 10:00 [PATCH] mm/page-writeback: Raise wb_thresh to prevent write blocking with strictlimit Jim Zhao
2024-10-23 23:24 ` Andrew Morton
2024-10-24 6:09 ` Jim Zhao
2024-10-24 6:20 ` Andrew Morton
2024-10-24 7:29 ` Jim Zhao
2024-10-26 0:02 ` Andrew Morton [this message]
2024-11-01 7:17 ` Jim Zhao
2024-11-07 15:32 ` Jan Kara
2024-11-08 3:19 ` Jim Zhao
2024-11-08 22:02 ` Jan Kara
2024-11-12 8:45 ` Jim Zhao
2024-11-13 10:07 ` Jan Kara
2024-11-19 11:44 ` [PATCH v2] mm/page-writeback: raise " Jim Zhao
2024-11-19 12:29 ` [PATCH v2] mm/page-writeback: Raise " Jim Zhao
2024-11-20 8:03 ` Kemeng Shi
2024-11-21 8:05 ` Jim Zhao
2024-12-12 12:32 ` Kemeng Shi
2024-11-20 11:57 ` Jan Kara
2024-11-21 10:20 ` Jim Zhao
2024-11-21 11:49 ` [PATCH v2] mm/page-writeback: raise " Jan Kara
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=20241025170222.0ced663e778935946ea1c9fa@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jimzhao.ai@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 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).