From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [45.249.212.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5CB1E846D for ; Sat, 4 Jan 2025 00:59:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.249.212.190 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1735952357; cv=none; b=r9DbmbMq5xoF0zKV8Bqye7/pO46T3AWG62kyn3PL52WnMGqtbrkCnMrMDfu+XhDG5L+9Fmf82+sDUEAXM5CKr2NgB4jRGRojsmHBwyZ19snOPvqmW/BOJWhbAp3zVkMW4jXoUX3B2QCoWSvv8uR6al+7qxbr7h/WRA36BeIbZpY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1735952357; c=relaxed/simple; bh=eakcWjcno7a8teq3+SeBdAJflC6NuWwHe+muNWecE/c=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=WYsn0oGRmlK6bCYfX8UUGcDEGjPJMioLLE8u/y9Lz+Vv1IxW2UXnKfw1hptfxCGh6kk/Egl+S2RGx97A9tB+Fx03SZ6culD/Fhxv/Eir3mjNPoMcIYung4BqmPjY0kVeTHXr1rtimxcwdQYnm93aICdEy3zjs8T9qZAnIQsDBGY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=45.249.212.190 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.19.163.44]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4YQ27f3tdlz2DjnC; Sat, 4 Jan 2025 08:56:14 +0800 (CST) Received: from kwepemd100013.china.huawei.com (unknown [7.221.188.163]) by mail.maildlp.com (Postfix) with ESMTPS id 5728314011D; Sat, 4 Jan 2025 08:59:10 +0800 (CST) Received: from [10.67.109.79] (10.67.109.79) by kwepemd100013.china.huawei.com (7.221.188.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.34; Sat, 4 Jan 2025 08:59:09 +0800 Message-ID: <07cafef3-464e-4311-b147-e80761ada7c1@huawei.com> Date: Sat, 4 Jan 2025 08:59:08 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH mm-unstable v4 0/7] mm/mglru: performance optimizations To: Andrew Morton , Yu Zhao CC: , References: <20241231043538.4075764-1-yuzhao@google.com> <20250102160314.20813f37b0bf748c3a06e877@linux-foundation.org> Content-Language: en-US From: chenridong In-Reply-To: <20250102160314.20813f37b0bf748c3a06e877@linux-foundation.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: dggems705-chm.china.huawei.com (10.3.19.182) To kwepemd100013.china.huawei.com (7.221.188.163) On 2025/1/3 8:03, Andrew Morton wrote: > On Mon, 30 Dec 2024 21:35:31 -0700 Yu Zhao 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