From: Tejun Heo <tj@kernel.org>
To: Kemeng Shi <shikemeng@huaweicloud.com>
Cc: willy@infradead.org, akpm@linux-foundation.org, jack@suse.cz,
hcochran@kernelspring.com, axboe@kernel.dk, mszeredi@redhat.com,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Fix and cleanups to page-writeback
Date: Wed, 1 May 2024 06:16:26 -1000 [thread overview]
Message-ID: <ZjJq2uvuXZoZ5aj3@slm.duckdns.org> (raw)
In-Reply-To: <20240425131724.36778-1-shikemeng@huaweicloud.com>
On Thu, Apr 25, 2024 at 09:17:20PM +0800, Kemeng Shi wrote:
> v1->v2:
> -rebase on up-to-date tree.
> -add test result in "mm: correct calculation of wb's bg_thresh in cgroup
> domain"
> -drop "mm: remove redundant check in wb_min_max_ratio"
> -collect RVB from Matthew to "mm: remove stale comment __folio_mark_dirty"
>
> This series contains some random cleanups and a fix to correct
> calculation of wb's bg_thresh in cgroup domain. More details can
> be found respective patches. Thanks!
Isn't this series already in -mm? Why is this being reposted? What tree is
this based on? Please provide more context to help reviewing the patches.
Thanks.
--
tejun
next prev parent reply other threads:[~2024-05-01 16:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 13:17 Kemeng Shi
2024-04-25 13:17 ` [PATCH v2 1/4] mm: enable __wb_calc_thresh to calculate dirty background threshold Kemeng Shi
2024-05-03 9:11 ` Jan Kara
2024-04-25 13:17 ` [PATCH v2 2/4] mm: correct calculation of wb's bg_thresh in cgroup domain Kemeng Shi
2024-05-03 9:30 ` Jan Kara
2024-05-07 1:16 ` Kemeng Shi
2024-05-07 13:28 ` Jan Kara
2024-04-25 13:17 ` [PATCH v2 3/4] mm: call __wb_calc_thresh instead of wb_calc_thresh in wb_over_bg_thresh Kemeng Shi
2024-05-03 9:31 ` Jan Kara
2024-04-25 13:17 ` [PATCH v2 4/4] mm: remove stale comment __folio_mark_dirty Kemeng Shi
2024-05-03 9:31 ` Jan Kara
2024-05-01 16:16 ` Tejun Heo [this message]
2024-05-06 1:25 ` [PATCH v2 0/4] Fix and cleanups to page-writeback Kemeng Shi
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=ZjJq2uvuXZoZ5aj3@slm.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hcochran@kernelspring.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mszeredi@redhat.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