From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta0.migadu.com (out-53.mta0.migadu.com [91.218.175.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2805D4D9F7A for ; Fri, 25 Sep 2026 19:36:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.53 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790365016; cv=none; b=OFWwFWarAGZVnQDQSclKe6cCGap5V79ARH8QYK29anhu7LCS3yAVU4cquVi3iLSDmd4l21J9I4Dsb7AVJklUhrMEmbDBHr1Jx9qdW27Obh2geXLg1fRcZQqAYAhllTRkoKFBsJkMTELBxIW+PniPDU7PobG7JdoDkCBJTxU92EA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790365016; c=relaxed/simple; bh=M4/lST7zD2Erdwe6/sNV3cFEsUbk898lwUHJrduDZXw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Uv9b4ejQQybfCvYjRZw2zMjGRCY0rcxvctioi492c/Z30utbeR3Z9p+iN18GUpe/uV5JNiXQx7nWwnPfhjGWWc5UyFy6REPYrTRVl1jVVaZRVaI9sD6isvQHbRe+2/duDFsqsmzUuq2Khv5plPMxAx6Hrhbw8ykpqrvvrHTtD/Q= 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=BRe/E98K; arc=none smtp.client-ip=91.218.175.53 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="BRe/E98K" X-Envelope-To: linux-kernel@vger.kernel.org DKIM-Signature: a=rsa-sha256; bh=M4/lST7zD2Erdwe6/sNV3cFEsUbk898lwUHJrduDZXw=; c=simple/simple; d=linux.dev; h=from:to:subject:date:message-id:mime-version:content-type; s=key1; t=1790365013; v=1; x=1790969813; b=BRe/E98KZSR63+gkjFk3hcCk4237lUFu1x2KoDAA8k5aPotOm9b/w6nC2l/Ev5et+DCZVvi8 qxNz7mPoX7PPvkBjB3x1V86N2fzl8Ogt+5xYJjhVf0TGLAiTqEjmKmLFmUhsaskLYaxulWzvJGS p91blrhC0QDIDgDcFfibKeY4= X-Envelope-To: linux-kernel@vger.kernel.org Received: by smtp.migadu.com with ESMTPS id 9b23b1b9c141f10f; Fri, 25 Sep 2026 19:36:52 +0000 X-Mizu-Trace-ID: 9b23b1b9c141f10f X-Migadu-Flow: FLOW_OUT Date: Fri, 25 Sep 2026 12:36:46 -0700 From: Shakeel Butt To: Kairui Song Cc: Chris Li , Nhat Pham , Rik van Riel , Baoquan He , Kairui Song , Johannes Weiner , Michal Hocko , Roman Gushchin , Yosry Ahmed , David Hildenbrand , Muchun Song , Kemeng Shi , Barry Song , YoungJun Park , Chengming Zhou , "Lorenzo Stoakes (Oracle)" , "Liam R. Howlett" , "Vlastimil Babka (SUSE)" , Mike Rapoport , Suren =?utf-8?B?QmFnaGRhc2FyeWFu77+8?= , Qi Zheng , Axel Rasmussen , Yuanchu Xie , Wei Xu , Gregory Price , Wenchao Hao , Jonathan Corbet , Hugh Dickins , Baolin Wang , Tejun Heo , Michal =?utf-8?Q?Koutn=C3=BD?= , Shuah Khan , Kunwu Chan , Meta kernel team , Linux Memory Management List , Linux Kernel Mailing List , linux-doc@vger.kernel.org, "open list:CONTROL GROUP - MEMORY RESOURCE CONTROLLER (MEMCG)" , Andrew Morton , Joshua Hahn Subject: Re: Path forward for Virtualized Swap? Message-ID: References: <7ee199ddee81bf8026688def82f78ad9db09be9e.camel@surriel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Fri, Sep 25, 2026 at 09:15:17PM +0800, Kairui Song wrote: [...] Thanks Kairui for very clear description of what you want and looking for. After reading your email, I think you want memsw support in v2. Currently you somehow are implementing memsw using memory.current and memory.swap.current. (I am assuming you need to subtract swapcache to avoid double counting.) To conclude, you want to use vswap (the aim is it to default) but you still want your way to implementing memsw keep working. Please correct me if I missed something. I am wondering if you really want memsw, why not propose memsw. Someone from tencent proposed memsw [1] previously, so why not continue that effort? I am pretty sure folks from Google (people who actually work on prodkernel there) will be happy to collaborate with you on that. [1] https://lore.kernel.org/20250319064148.774406-1-jingxiangzeng.cas@gmail.com/ Setting aside the memsw conversation, I think we should go back to the actual vswap conversation and list down what we agree on and where we still need discussion and decision. (I will take a stab at it and start a separate thread but still on this email and will use AI for the summary.)