From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,willy@infradead.org,tj@kernel.org,shikemeng@huaweicloud.com,akpm@linux-foundation.org
Subject: [folded-merged] writeback-factor-out-balance_wb_limits-to-remove-repeated-code-v3.patch removed from -mm tree
Date: Mon, 24 Jun 2024 21:16:24 -0700 [thread overview]
Message-ID: <20240625041624.96729C32782@smtp.kernel.org> (raw)
The quilt patch titled
Subject: writeback-factor-out-balance_wb_limits-to-remove-repeated-code-v3
has been removed from the -mm tree. Its filename was
writeback-factor-out-balance_wb_limits-to-remove-repeated-code-v3.patch
This patch was dropped because it was folded into writeback-factor-out-balance_wb_limits-to-remove-repeated-code.patch
------------------------------------------------------
From: Kemeng Shi <shikemeng@huaweicloud.com>
Subject: writeback-factor-out-balance_wb_limits-to-remove-repeated-code-v3
Date: Thu, 6 Jun 2024 11:35:47 +0800
add comment
Link: https://lkml.kernel.org/r/20240606033547.344376-1-shikemeng@huaweicloud.com
Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Cc: Tejun Heo <tj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/page-writeback.c | 4 ++++
1 file changed, 4 insertions(+)
--- a/mm/page-writeback.c~writeback-factor-out-balance_wb_limits-to-remove-repeated-code-v3
+++ a/mm/page-writeback.c
@@ -1805,6 +1805,10 @@ static inline void wb_dirty_exceeded(str
((dtc->dirty > dtc->thresh) || strictlimit);
}
+/*
+ * The limits fileds dirty_exceeded and pos_ratio won't be updated if wb is
+ * in freerun state. Please don't use these invalid fileds in freerun case.
+ */
static void balance_wb_limits(struct dirty_throttle_control *dtc,
bool strictlimit)
{
_
Patches currently in -mm which might be from shikemeng@huaweicloud.com are
writeback-factor-out-wb_bg_dirty_limits-to-remove-repeated-code.patch
writeback-add-general-function-domain_dirty_avail-to-calculate-dirty-and-avail-of-domain.patch
writeback-factor-out-domain_over_bg_thresh-to-remove-repeated-code.patch
writeback-factor-out-code-of-freerun-to-remove-repeated-code.patch
writeback-factor-out-wb_dirty_freerun-to-remove-more-repeated-freerun-code.patch
writeback-factor-out-balance_domain_limits-to-remove-repeated-code.patch
writeback-factor-out-wb_dirty_exceeded-to-remove-repeated-code.patch
writeback-factor-out-balance_wb_limits-to-remove-repeated-code.patch
reply other threads:[~2024-06-25 4:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240625041624.96729C32782@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=mm-commits@vger.kernel.org \
--cc=shikemeng@huaweicloud.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.