[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20230410213618.0d8b2b19a15376dfd49e3c53@linux-foundation.org>
Date: Mon, 10 Apr 2023 21:36:18 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: yizhou.tang@...pee.com
Cc: neilb@...e.com, tj@...nel.org, wufengguang@...wei.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
tangyeechou@...il.com, chunguang.xu@...pee.com, yue.zhao@...pee.com
Subject: Re: [PATCH] mm: Fix memcg writeback for rt tasks
On Tue, 4 Apr 2023 00:57:08 +0800 yizhou.tang@...pee.com wrote:
> From: Tang Yizhou <yizhou.tang@...pee.com>
>
> Neil said he didn't know what was wanted for realtime in the commit
> message of commit a37b0715ddf3 ("mm/writeback: replace PF_LESS_THROTTLE
> with PF_LOCAL_THROTTLE"). I think we need to distinguish between the
> global writeback and memcg writeback in domain_dirty_limits() for the
> rt tasks.
Why do you think this?
> Fixes: a53eaff8c119 ("MM: increase safety margin provided by PF_LESS_THROTTLE")
In what way does it fix it? Please describe the user-visible effects
of this change.
Powered by blists - more mailing lists