From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 43B082FBDF9 for ; Fri, 14 Nov 2025 08:36:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763109379; cv=none; b=MsjwSG90qBLpxvlxtS1cLdJYR5O3wTWFEgeHcb9Sd2sgyhTeIhBUaCjirxILwuvRr3WCUfp5JvAXgJ0HaqTyY87GsOzvt0nG/5xVmc8lGUwUT2ejxB8hZb0GpmZI+WNrfPDpvYVm8VyFTXKeVY7zFmk/kkFpEDMX/9/xX+MOeeE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763109379; c=relaxed/simple; bh=eWGYBsLmz/5LRmgat5KjGwo91+k4m6JF84j9BzT5HWE=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=oZn7lrGTsSsQodrGkq1g6de1rQNyqW+7WMuu4hD/uyPCsnCWN6x9jE2TTP8HeWJWuA/oLW+ke6adwRLmVHQlkracih4wVDopVKWt2NFCo1G+tUFHPnhIshFn8j89PG2gmU+OkzFujSul0RpF3MjTfv+4jOXVenjJfmOP1W+dmu0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=F2Owpah+; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="F2Owpah+" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2FD9EC4CEF8; Fri, 14 Nov 2025 08:36:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1763109378; bh=eWGYBsLmz/5LRmgat5KjGwo91+k4m6JF84j9BzT5HWE=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=F2Owpah+gT1P6oR4hero/YLaRllSRs7/IqzcWjr8T6aARmKxVkvyShYWYDdo42U09 I0tb8gvsHii5Z1jLRwgYMVs50vNUqptG5dKxPC9vcxPQg2pZG1p3TAjJ2/jhwYtuQ5 XbB6k3q6lLNhalnzHcv+m6fRwGqipdvwZ5RTzt9IoLYeQHATZNbll87iSb0q0sobVe icktECJLCoQY8NUs9bpqyPXgrzo3agn715qYlWap3mK9KzQ0xfVmOdtqisTZ9L389N KLCbRBEH3ZgdTT8voj9FzXxCxBT9xNVcd/CgNy4jFUL8qlhb/yv0gHAxBfaLbH7oZb sQLWG/OrVaYyQ== Message-ID: <5b481d76-638d-46d4-ad98-5508fc8b715e@kernel.org> Date: Fri, 14 Nov 2025 09:36:09 +0100 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/huge_memory.c: introduce folio_split_unmapped To: Balbir Singh , linux-kernel@vger.kernel.org, linux-mm@kvack.org, dri-devel@lists.freedesktop.org Cc: Andrew Morton , Zi Yan , Joshua Hahn , Rakie Kim , Byungchul Park , Gregory Price , Ying Huang , Alistair Popple , Oscar Salvador , Lorenzo Stoakes , Baolin Wang , "Liam R. Howlett" , Nico Pache , Ryan Roberts , Dev Jain , Barry Song , Lyude Paul , Danilo Krummrich , David Airlie , Simona Vetter , Ralph Campbell , =?UTF-8?Q?Mika_Penttil=C3=A4?= , Matthew Brost , Francois Dugast References: <20251114012228.2634882-1-balbirs@nvidia.com> From: "David Hildenbrand (Red Hat)" Content-Language: en-US In-Reply-To: <20251114012228.2634882-1-balbirs@nvidia.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 14.11.25 02:22, Balbir Singh wrote: > Unmapped was added as a parameter to __folio_split() and related > call sites to support splitting of folios already in the midst > of a migration. This special case arose for device private folio > migration since during migration there could be a disconnect between > source and destination on the folio size. Didn't I already comment that the subject should start with "mm/huge_memory: introduce ..." ? Yes I did: https://lore.kernel.org/all/048134fd-6a3d-4a6c-a2eb-9a9911c3b35f@kernel.org/ You know, I'm a busy man, can you *please* * take better care of addressing all previous comments? * wait more than 12 h after asking a question before you resend? -- Cheers David