linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Kemeng Shi <shikemeng@huaweicloud.com>
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 3/4] writeback: add wb_monitor.py script to monitor writeback info on bdi
Date: Mon, 22 Apr 2024 08:32:52 -1000	[thread overview]
Message-ID: <ZiatVDpNb59kmT9V@slm.duckdns.org> (raw)
In-Reply-To: <20240422164808.13627-4-shikemeng@huaweicloud.com>

On Tue, Apr 23, 2024 at 12:48:07AM +0800, Kemeng Shi wrote:
> Add wb_monitor.py script to monitor writeback information on backing dev
> which makes it easier and more convenient to observe writeback behaviors
> of running system.
> 
> The wb_monitor.py script is written based on wq_monitor.py.
> 
> Following domain hierarchy is tested:
>                 global domain (320G)
>                 /                 \
>         cgroup domain1(10G)     cgroup domain2(10G)
>                 |                 |
> bdi            wb1               wb2
> 
> The wb_monitor.py script output is as following:
> ./wb_monitor.py 252:16 -c
>                   writeback  reclaimable   dirtied   written    avg_bw
> 252:16_1                  0            0         0         0    102400
> 252:16_4284             672       820064   9230368   8410304    685612
> 252:16_4325             896       819840  10491264   9671648    652348
> 252:16                 1568      1639904  19721632  18081952   1440360
> 
>                   writeback  reclaimable   dirtied   written    avg_bw
> 252:16_1                  0            0         0         0    102400
> 252:16_4284             672       820064   9230368   8410304    685612
> 252:16_4325             896       819840  10491264   9671648    652348
> 252:16                 1568      1639904  19721632  18081952   1440360
> ...
> 
> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
> Suggested-by: Tejun Heo <tj@kernel.org>

Acked-by: Tejun Heo <tj@kernel.org>

Thanks.

-- 
tejun


  reply	other threads:[~2024-04-22 18:32 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
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 [this message]
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=ZiatVDpNb59kmT9V@slm.duckdns.org \
    --to=tj@kernel.org \
    --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=shikemeng@huaweicloud.com \
    --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