From: chenridong <chenridong@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>, Yu Zhao <yuzhao@google.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH mm-unstable v4 0/7] mm/mglru: performance optimizations
Date: Sat, 4 Jan 2025 08:59:08 +0800 [thread overview]
Message-ID: <07cafef3-464e-4311-b147-e80761ada7c1@huawei.com> (raw)
In-Reply-To: <20250102160314.20813f37b0bf748c3a06e877@linux-foundation.org>
On 2025/1/3 8:03, Andrew Morton wrote:
> On Mon, 30 Dec 2024 21:35:31 -0700 Yu Zhao <yuzhao@google.com> wrote:
>
>> This series improves performance for some previously reported test
>> cases. Most of the code changes gathered here has been floating on the
>> mailing list [1][2]. They are now properly organized and have gone
>> through various benchmarks on client and server devices, including
>> Android, FIO, memcached, multiple VMs and MongoDB.
>
> This series has significant conflicts with the patch "mm: vmscan: retry
> folios written back while isolated for traditional LRU". It appears
> that "mm: vmscan: retry folios written back while isolated for
> traditional LRU" is due for an update and that more discussion is
> needed, so I shall drop this version of "mm: vmscan: retry folios
> written back while isolated for traditional LRU" from mm-unstable.
Hi, Andrew and Yu, does this mean I should resend a new version that
fixes the conflict and updates the message?
Best regards,
Ridong
next prev parent reply other threads:[~2025-01-04 0:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 4:35 [PATCH mm-unstable v4 0/7] mm/mglru: performance optimizations Yu Zhao
2024-12-31 4:35 ` [PATCH mm-unstable v4 1/7] mm/mglru: clean up workingset Yu Zhao
2024-12-31 4:35 ` [PATCH mm-unstable v4 2/7] mm/mglru: optimize deactivation Yu Zhao
2024-12-31 4:35 ` [PATCH mm-unstable v4 3/7] mm/mglru: rework aging feedback Yu Zhao
2025-01-07 17:14 ` Kairui Song
2025-01-13 6:51 ` Yu Zhao
2025-01-15 17:56 ` Kairui Song
2024-12-31 4:35 ` [PATCH mm-unstable v4 4/7] mm/mglru: rework type selection Yu Zhao
2024-12-31 4:35 ` [PATCH mm-unstable v4 5/7] mm/mglru: rework refault detection Yu Zhao
2024-12-31 4:35 ` [PATCH mm-unstable v4 6/7] mm/mglru: rework workingset protection Yu Zhao
2024-12-31 4:35 ` [PATCH mm-unstable v4 7/7] mm/mglru: fix PTE-mapped large folios Yu Zhao
2025-01-03 0:03 ` [PATCH mm-unstable v4 0/7] mm/mglru: performance optimizations Andrew Morton
2025-01-04 0:59 ` chenridong [this message]
2025-01-04 2:21 ` Andrew Morton
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=07cafef3-464e-4311-b147-e80761ada7c1@huawei.com \
--to=chenridong@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yuzhao@google.com \
/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