From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-181.mta0.migadu.com (out-181.mta0.migadu.com [91.218.175.181]) (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 C9461246766 for ; Thu, 14 May 2026 02:35:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.181 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778726152; cv=none; b=kiRY/XXr6KX4griD4/WPu7OEDMPBwm6g4bWDbMBw/SEffS/PbeUwIEjOOC3OOUoD5IVNOEFcpqt37aXyuieyYSmAh6/Ir0vPnv5fKNcl6nadhjMRN1Kl58D3kBHBdzM1x+ha5LoKBEdZZPo6gqRS4jSoJzgBWN/cmmIc/pSnHFI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778726152; c=relaxed/simple; bh=z7nY4qLl8VtihNlm9SkvX/PnnWztJhIkTuHkivLq/Wg=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Message-Id:References:To; b=PuSsROSkv/GgKHLRVWK4OoIQ0R8W+J9pt9fNSkSXg791ZXHkzBHas+OdtK1mKTgxlnAfjxDYJeb8W8h2x6r7elzVGUbqs4pXRK/Fd3Ytz+yxXUZQNhr0G4ovr+Dsj/PlXhBCTGMtsNv4nKMDp1gJc5jOdMByKcKehZXcHtvC/N8= 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=G+ZKSnnC; arc=none smtp.client-ip=91.218.175.181 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="G+ZKSnnC" Content-Type: text/plain; charset=us-ascii DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1778726147; 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=L4R4J3RwmjA53m4R5RtoEscHz/YnvUKFxIVx8Fa4X0Y=; b=G+ZKSnnCixAkusAvNx6AviFC3l0Yw71F5NKxYrgFc01CFGNA8UCorUPtvcKSg93EZexN6o LY/S4mSvSVORzskYnSqY3BqBXcs53W74fBdTaaxkCqDTFWUT87NxnO7gEnFac81DF2uyN/ sbLMEsPwxcBoPKg6XFBJX2woeDspPkc= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.500.181\)) Subject: Re: [PATCH v2 00/69] mm: Generalize HVO for HugeTLB and device DAX X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Muchun Song In-Reply-To: <20260513104640.b0f02b844c57f92bc954878e@linux-foundation.org> Date: Thu, 14 May 2026 10:34:56 +0800 Cc: Muchun Song , David Hildenbrand , Oscar Salvador , Michael Ellerman , Madhavan Srinivasan , Lorenzo Stoakes , "Liam R . Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , Nicholas Piggin , Christophe Leroy , Ackerley Tng , Frank van der Linden , aneesh.kumar@linux.ibm.com, joao.m.martins@oracle.com, linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org Content-Transfer-Encoding: quoted-printable Message-Id: <72F6690C-D94B-4398-87C7-4611A96C50AC@linux.dev> References: <20260513130542.35604-1-songmuchun@bytedance.com> <20260513104640.b0f02b844c57f92bc954878e@linux-foundation.org> To: Andrew Morton X-Migadu-Flow: FLOW_OUT > On May 14, 2026, at 01:46, Andrew Morton = wrote: >=20 > On Wed, 13 May 2026 21:04:28 +0800 Muchun Song = wrote: >=20 >> In this series, HVO is redefined as Hugepage Vmemmap Optimization: a >> general vmemmap optimization model for large hugepage-backed = mappings, >> rather than a HugeTLB-only implementation detail. >>=20 >> The existing code grew around the original HugeTLB-specific HVO path, >> while device DAX developed similar but separate vmemmap optimization >> handling. As a result, the current implementation carries duplicated >> logic, boot-time special cases, and subsystem-specific interfaces = around >> what is fundamentally the same sparse-vmemmap optimization. >>=20 >> This series generalizes that optimization into a common framework = used >> by both HugeTLB and device DAX. >>=20 >> The first few patches include some minor bug fixes found during = AI-aided >> review of the current code. These fixes are not the main goal of the >> series, but the later refactoring and unification work depends on = them, >> so they are included here as preparatory changes. >>=20 >> The series then reworks the relevant early boot and sparse >> initialization paths, introduces a generic section-based = sparse-vmemmap >> optimization infrastructure, switches HugeTLB and device DAX over to = the >> shared implementation, and removes the old special-case code. >>=20 >> ... >>=20 >> 46 files changed, 743 insertions(+), 1812 deletions(-) >=20 > Gulp. Sorry for a so big series to refactor lots of things. >=20 > I think the first 15ish patches (little fixes and cleanups and > refactorings) are ready to go in immediately? Overall, I believe the first 12 patches (excluding the bugfixes) have already been reviewed by Mike and are theoretically ready to be merged. >=20 > Perhaps you could prepare such things as a separate series. Or tell = me > which ones are suitable and I'll fudge up a [0/N]? I'd prefer to group the first 19 patches into a single series (titled "Refactor bootmem gigantic hugepage allocation"). Therefore, I suggest waiting for feedback from other maintainers/reviewers; once patches 13-19 pass review, I will send them out as a standalone series. Muchun, Thanks.