From: Kemeng Shi <shikemeng@huaweicloud.com>
To: Tejun Heo <tj@kernel.org>
Cc: akpm@linux-foundation.org, willy@infradead.org, jack@suse.cz,
bfoster@redhat.com, dsterba@suse.com, mjguzik@gmail.com,
dhowells@redhat.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4 2/4] writeback: support retrieving per group debug writeback stats of bdi
Date: Tue, 23 Apr 2024 09:15:16 +0800 [thread overview]
Message-ID: <7e8d85c0-8b36-9c47-1411-f7077e5c0cd8@huaweicloud.com> (raw)
In-Reply-To: <ZiatOJDzICT9e6pi@slm.duckdns.org>
on 4/23/2024 2:32 AM, Tejun Heo wrote:
> Hello,
>
> On Tue, Apr 23, 2024 at 12:48:06AM +0800, Kemeng Shi wrote:
>> Add /sys/kernel/debug/bdi/xxx/wb_stats to show per group writeback stats
>> of bdi.
>>
>> Following domain hierarchy is tested:
>> global domain (320G)
>> / \
>> cgroup domain1(10G) cgroup domain2(10G)
>> | |
>> bdi wb1 wb2
>>
>> /* per wb writeback info of bdi is collected */
>> cat /sys/kernel/debug/bdi/252:16/wb_stats
>> WbCgIno: 1
>> WbWriteback: 0 kB
>> WbReclaimable: 0 kB
>> WbDirtyThresh: 0 kB
>> WbDirtied: 0 kB
>> WbWritten: 0 kB
>> WbWriteBandwidth: 102400 kBps
>> b_dirty: 0
>> b_io: 0
>> b_more_io: 0
>> b_dirty_time: 0
>> state: 1
>> WbCgIno: 4094
>> WbWriteback: 54432 kB
>> WbReclaimable: 766080 kB
>> WbDirtyThresh: 3094760 kB
>> WbDirtied: 1656480 kB
>> WbWritten: 837088 kB
>> WbWriteBandwidth: 132772 kBps
>> b_dirty: 1
>> b_io: 1
>> b_more_io: 0
>> b_dirty_time: 0
>> state: 7
>> WbCgIno: 4135
>> WbWriteback: 15232 kB
>> WbReclaimable: 786688 kB
>> WbDirtyThresh: 2909984 kB
>> WbDirtied: 1482656 kB
>> WbWritten: 681408 kB
>> WbWriteBandwidth: 124848 kBps
>> b_dirty: 0
>> b_io: 1
>> b_more_io: 0
>> b_dirty_time: 0
>> state: 7
>>
>> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
>
> Maybe it'd be useful to delineate each wb better in the output? It's a bit
> difficult to parse visually. Other than that,
Sorry for this. A blank line was added at end of each wb in this patch but I
forgot to update the changelog.
As there is some kunit build problem reported, I will correct changelog with
the fix to build problem.
Thanks a lot for review.
Kemeng
>
> Acked-by: Tejun Heo <tj@kernel.org>
>
> Thanks.
>
next prev parent reply other threads:[~2024-04-23 1:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 16:48 [PATCH v4 0/4] Improve visibility of writeback Kemeng Shi
2024-04-22 15:04 ` Matthew Wilcox
2024-04-22 16:48 ` [PATCH v4 1/4] writeback: collect stats of all wb of bdi in bdi_debug_stats_show Kemeng Shi
2024-04-22 18:23 ` Tejun Heo
2024-04-22 16:48 ` [PATCH v4 2/4] writeback: support retrieving per group debug writeback stats of bdi Kemeng Shi
2024-04-22 18:32 ` Tejun Heo
2024-04-23 1:15 ` Kemeng Shi [this message]
2024-04-23 0:44 ` SeongJae Park
2024-04-23 1:29 ` Kemeng Shi
2024-04-22 16:48 ` [PATCH v4 3/4] writeback: add wb_monitor.py script to monitor writeback info on bdi Kemeng Shi
2024-04-22 18:32 ` Tejun Heo
2024-04-22 16:48 ` [PATCH v4 4/4] writeback: rename nr_reclaimable to nr_dirty in balance_dirty_pages Kemeng Shi
2024-04-22 18:33 ` Tejun Heo
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=7e8d85c0-8b36-9c47-1411-f7077e5c0cd8@huaweicloud.com \
--to=shikemeng@huaweicloud.com \
--cc=akpm@linux-foundation.org \
--cc=bfoster@redhat.com \
--cc=dhowells@redhat.com \
--cc=dsterba@suse.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjguzik@gmail.com \
--cc=tj@kernel.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