From: jim zhao <jimzhao.ai@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
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: Thu, 24 Oct 2024 14:52:18 +0800 [thread overview]
Message-ID: <CADDbF7VH+dC=Tt77OUd9Zdv91FCR9KvRfKQ4-McJp7QXCuxD7Q@mail.gmail.com> (raw)
In-Reply-To: <20241023232042.f9373f9f826ceae2a4f4da35@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
> Thanks, but it's still unclear how this impacts our users. How lenghty
> are these pauses?
The length maybe related to device writeback bandwidth.
Under normal bandwidth, each pause may last around 4ms and several times as
shown in the trace above.
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.
[-- Attachment #2: Type: text/html, Size: 515 bytes --]
next prev parent reply other threads:[~2024-12-05 15:22 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
2024-10-24 6:09 ` Jim Zhao
2024-10-24 6:20 ` Andrew Morton
2024-10-24 6:52 ` jim zhao [this message]
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='CADDbF7VH+dC=Tt77OUd9Zdv91FCR9KvRfKQ4-McJp7QXCuxD7Q@mail.gmail.com' \
--to=jimzhao.ai@gmail.com \
--cc=akpm@linux-foundation.org \
--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