From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta1.migadu.com (out-247.mta1.migadu.com [95.215.58.247]) (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 09DAF1E5018 for ; Wed, 14 Oct 2026 01:30:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.247 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791941461; cv=none; b=YgU+kdCEzj4EimCkeMEPgdlnN5hdrRJH7E2la7ytUe8nvYmJaNVc5aBJxnlAhaYFQYjxjDjwWSWacuHZ7ZaemxP+V0cZi/L0b3DoxLZlZodpsCuuNSqtSLty3+r3zM5Y6MNa2lPD4rwhcOQLYwDcqJffEuM5XHFv25ODf5fp2wM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791941461; c=relaxed/simple; bh=5ROt2655uPgI977PSMUmpSlu+2sAipPFwrJ1t+HxYEo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=IiNiylrgs2jUsGRBbwCzTdCnw8dOdpnPQEHo8Jlh2C3jqFOWrg0/NrpsPGoszRsA1qKa99BaHU2Dw+erU+1XhX4laRRxrpusgXSUPC+qe3tF84NLwTqxrs9oi6l36+LVe/h/vZZMjtk4dOaeJ+N5IEKGXaxEszFVdRCtpMH6Y+U= 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=ScbTqj69; arc=none smtp.client-ip=95.215.58.247 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="ScbTqj69" X-Envelope-To: linux-kernel@vger.kernel.org DKIM-Signature: a=rsa-sha256; bh=5ROt2655uPgI977PSMUmpSlu+2sAipPFwrJ1t+HxYEo=; c=simple/simple; d=linux.dev; h=from:to:subject:date:message-id:mime-version:content-type; s=key1; t=1791941457; v=1; x=1792546257; b=ScbTqj6977N0M+TFrc7aOMq0QtOCFzCqsar6DizDZ8OLRua3ipU5zr4QYPNQwrovmdxmpJq+ iAk08MPk3gG5UICLkRQcnLoX/ynb0qO+/Z5xNy1s26CratQRQL1dr4L4/CKmwkEc8BhfmrKFJYz jSFVRmvRQJlvp9v1XEnsEWjA= X-Envelope-To: linux-kernel@vger.kernel.org Received: by mta10.migadu.com with ESMTPS id 7d27739f63868d36; Wed, 14 Oct 2026 01:30:34 +0000 X-Mizu-Trace-ID: 7d27739f63868d36 X-Migadu-Flow: FLOW_OUT Date: Wed, 14 Oct 2026 09:30:29 +0800 From: Baoquan He To: "David Hildenbrand (Arm)" Cc: Chris Li , Nhat Pham , Kairui Song , Johannes Weiner , Michal Hocko , Roman Gushchin , Shakeel Butt , Yosry Ahmed , 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 , Rik van Riel , Gregory Price , Wenchao Hao , Jonathan Corbet , Hugh Dickins , Baolin Wang , Tejun Heo , Michal =?iso-8859-1?Q?Koutn=FD?= , 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: <5fdb3777-95a2-48f9-bb38-aa4ba3c96a81@kernel.org> <5ca344de-bc34-4a9b-ab85-f553811a1d9c@kernel.org> <5c8a2b7b-b76d-4bba-92e1-ec3d66794273@kernel.org> 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=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5c8a2b7b-b76d-4bba-92e1-ec3d66794273@kernel.org> On 10/05/26 at 01:06pm, David Hildenbrand (Arm) wrote: > On 9/22/26 15:38, Chris Li wrote: > > On Mon, Sep 21, 2026 at 8:56 AM Nhat Pham wrote: > >> > >> On Fri, Sep 18, 2026 at 11:50 PM Chris Li wrote: > >>> No that time slot is too late for Asia developers. I don't think we > >>> should use that time slot for swap alignment. > >>> > >>> We should find a time slot more friendly to Asia. > >> > >> Any time slot would have that kind of problem. We're spread out across > >> the globe. > >> > >> Let's just use a standardized time slot we have for MM alignment sessions. > > > > There are more swap maintainers in Asia than in the US + Europe, at > > least based on the maintainer file. Please be more inclusive. If the > > alignment is done without key stakeholders, it miss the point. > > > > Sigh, we can't even align on a time slot. > > > > In that case, let's keep discussing on the mailing list. At least it > > is accessible to every one. > > Looking at the mailing list, that approach doesn't seem to work. > > Finding a time slot that makes US, Europe and Asia happy is ... tricky. > > 1 AM is certainly unpleasant. > > US vs. Asia is also tricky, but doable. > > China 8AM vs. US West Coast 5PM? > > China 9AM vs. US West Coast 6PM? > > (Europe is 2AM vs. 3AM, who besides me from Europe would join?) Hi David, Thanks for the suggestion and for organizing this meeting. Both time slot is fine to me. I also support collecting the concerns or issues people care about in advance and discussing them during the meeting. Thanks Baoquan