From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-179.mta1.migadu.com (out-179.mta1.migadu.com [95.215.58.179]) (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 67BB12DECDE for ; Sat, 18 Jul 2026 09:35:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.179 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784367320; cv=none; b=CbGHHPOP7kdzHXXIXLIrB/yLZ0cAVtA9Do5/Ec2e5eU1h+kL7g9p2zm+pHuH3MvyEF3kq+cyYGwhVLWVh5F988eNe7YbF7ZcLn+ag1p6mKKNLdfT+D34HiF4PV7W6txHRhFwJyCD/1X75VqsLmw7O3SsBIj2S3MdegQ14Tx1mjk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784367320; c=relaxed/simple; bh=iZ3BzXmq4tq8QuVWv2Th7SrUzRu3tt84ZGk6QIKzp7s=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=rNUtxAKMF3eZAmmLFtXuPvsvS88zcGiEmQEUQxNhf6hQz1GFg/9DawSy4ZNkT2Sm7rcJlsv7+vR/kNinI6iaf7PiByq9o6t0XMP4YfE12mUQ0qKZSaYyZD0q/mrksKDAQ6CSr7IeSlFBgrSB0n9d0hbFngMtNja4qteAaZu08sc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=Qq7iSJfW; arc=none smtp.client-ip=95.215.58.179 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="Qq7iSJfW" Message-ID: <68b3f507-ab35-4510-b3d7-0e4ff880bca7@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1784367315; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=loAjxjtaw3yEGqZqUekqy0OrttrEXSBviGMwLrtQasc=; b=Qq7iSJfWqxcHDcLpE/utZ62IzQJ9fCVicfXNUVZeICKwe/Gmvq7SgqEGXp8KEO6MUxn29N qfs418FBLTvDH4cBp/WrIbQCrvE7iQ3GI2iwBNzzuOp76G2iE0Pc/PUcI0WzHHH/p3FUTS ghRJIRx+tAm1DMUUsgFcQiOer7QHSlA= Date: Sat, 18 Jul 2026 17:34:59 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH 0/3] mm/vmscan: fix swappiness=max and clean up per-node proactive reclaim To: Andrew Morton Cc: Johannes Weiner , Kairui Song , Qi Zheng , Shakeel Butt , Barry Song , Axel Rasmussen , Yuanchu Xie , Wei Xu , David Hildenbrand , Michal Hocko , Lorenzo Stoakes , Zhongkun He , Muchun Song , Davidlohr Bueso , Roman Gushchin , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Ridong Chen References: <20260717113300.214717-1-ridong.chen@linux.dev> <20260717125327.cd3e3cc4e6cc28b0855e6502@linux-foundation.org> Content-Language: en-US X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Ridong Chen In-Reply-To: <20260717125327.cd3e3cc4e6cc28b0855e6502@linux-foundation.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT On 7/18/2026 3:53 AM, Andrew Morton wrote: > On Fri, 17 Jul 2026 19:32:57 +0800 Ridong wrote: > >> From: Ridong Chen >> >> Two fixes and one cleanup. >> >> Patch 1 fixes "swappiness=max": the anon-only test in get_scan_count() >> sat after the "cannot reclaim anon" check, so when no anon was >> reclaimable the request fell back to SCAN_FILE and evicted page cache >> instead. >> >> Patch 2 fixes reclaim_store() collapsing every error into -EAGAIN, so >> callers can no longer tell an invalid argument from a busy interface; >> propagate the real error code, matching the memcg path. >> >> Patch 3 drops the now-unused gfp_mask parameter from __node_reclaim(). > > Thanks. Sashiko want to know whether MGLRU should also be fixed: > https://sashiko.dev/#/patchset/20260717113300.214717-1-ridong.chen@linux.dev > Yes, it should be fixed. I will add a patch to fix it. -- Best regards, Ridong