From: Andrew Morton <akpm@linux-foundation.org>
To: Jim Zhao <jimzhao.ai@gmail.com>
Cc: willy@infradead.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/page-writeback: Raise wb_thresh to prevent write blocking with strictlimit
Date: Wed, 23 Oct 2024 16:24:47 -0700 [thread overview]
Message-ID: <20241023162447.2bf480b4ce590fdeb8b6c52d@linux-foundation.org> (raw)
In-Reply-To: <20241023100032.62952-1-jimzhao.ai@gmail.com>
On Wed, 23 Oct 2024 18:00:32 +0800 Jim Zhao <jimzhao.ai@gmail.com> wrote:
> With the strictlimit flag, wb_thresh acts as a hard limit in
> balance_dirty_pages() and wb_position_ratio(). When device write
> operations are inactive, wb_thresh can drop to 0, causing writes to
> be blocked. The issue occasionally occurs in fuse fs, particularly
> with network backends, the write thread is blocked frequently during
> a period. To address it, this patch raises the minimum wb_thresh to a
> controllable level, similar to the non-strictlimit case.
Please tell us more about the userspace-visible effects of this. It
*sounds* like a serious (but occasional) problem, but that is unclear.
And, very much relatedly, do you feel this fix is needed in earlier
(-stable) kernels?
next prev parent reply other threads:[~2024-10-23 23:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 10:00 Jim Zhao
2024-10-23 23:24 ` Andrew Morton [this message]
2024-10-24 6:09 ` Jim Zhao
2024-10-24 6:20 ` Andrew Morton
2024-10-24 6:52 ` jim zhao
2024-10-24 7:29 ` Jim Zhao
2024-10-26 0:02 ` Andrew Morton
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=20241023162447.2bf480b4ce590fdeb8b6c52d@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