[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <07cafef3-464e-4311-b147-e80761ada7c1@huawei.com>
Date: Sat, 4 Jan 2025 08:59:08 +0800
From: chenridong <chenridong@...wei.com>
To: Andrew Morton <akpm@...ux-foundation.org>, Yu Zhao <yuzhao@...gle.com>
CC: <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH mm-unstable v4 0/7] mm/mglru: performance optimizations
On 2025/1/3 8:03, Andrew Morton wrote:
> On Mon, 30 Dec 2024 21:35:31 -0700 Yu Zhao <yuzhao@...gle.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
Powered by blists - more mailing lists