linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Zhao <jimzhao.ai@gmail.com>
To: jack@suse.cz, akpm@linux-foundation.org
Cc: jimzhao.ai@gmail.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	shikemeng@huaweicloud.com, willy@infradead.org
Subject: Re: [PATCH v2] mm/page-writeback: Raise wb_thresh to prevent write blocking with strictlimit
Date: Thu, 21 Nov 2024 18:20:47 +0800	[thread overview]
Message-ID: <20241121102047.610700-1-jimzhao.ai@gmail.com> (raw)
In-Reply-To: <20241120115731.gzxozbnb6eazhil7@quack3>

> On Tue 19-11-24 20:29:22, Jim Zhao wrote:
> > Thanks, Jan, I just sent patch v2, could you please review it ?
>
> Yes, the patch looks good to me.
>
> >
> > And I found the debug info in the bdi stats.
> > The BdiDirtyThresh value may be greater than DirtyThresh, and after
> > applying this patch, the value of BdiDirtyThresh could become even
> > larger.
> >
> > without patch:
> > ---
> > root@ubuntu:/sys/kernel/debug/bdi/8:0# cat stats
> > BdiWriteback:                0 kB
> > BdiReclaimable:             96 kB
> > BdiDirtyThresh:        1346824 kB
>
> But this is odd. The machine appears to have around 3GB of memory, doesn't
> it? I suspect this is caused by multiple cgroup-writeback contexts
> contributing to BdiDirtyThresh - in fact I think the math in
> bdi_collect_stats() is wrong as it is adding wb_thresh() calculated based
> on global dirty_thresh for each cgwb whereas it should be adding
> wb_thresh() calculated based on per-memcg dirty_thresh... You can have a
> look at /sys/kernel/debug/bdi/8:0/wb_stats file which should have correct
> limits as far as I'm reading the code.

Thanks for review!
Yes, It should be caused by multiple cgroup-writeback with bdi_collect_stats issue.

@Andrew, 
I sent patch v2 according Jan's suggestion. 
Since patch v1 already in tree. So I sent out the diff of v1 -> v2:
https://lore.kernel.org/all/20241121100539.605818-1-jimzhao.ai@gmail.com/
Could you please review it, thanks!

Jim Zhao

  reply	other threads:[~2024-11-21 10:20 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
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 [this message]
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=20241121102047.610700-1-jimzhao.ai@gmail.com \
    --to=jimzhao.ai@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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;
as well as URLs for NNTP newsgroup(s).