From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 864D435675B for ; Tue, 9 Jun 2026 14:33:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781015627; cv=none; b=ClW+aMaQsdodAcG2aIHY5/+uObahJJz63IlPP6O5dWa1rZ/ANa9ztbgjDi0dhZyONV+6VS9T9Bl4L33ZEmrz9gEaMkLs53/2r3ZEQxB7G5CFFl4K4d9oYzJIXHoQtgyH8kCpyR8WR/Grj1oF6cG1yVhYCE+AiWh8eb+zQrRbuxE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781015627; c=relaxed/simple; bh=vgUpJ95jV804b8pioNKJRETKqdxJJYAZymPVTpfJdwE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=IeK24SS1EtNAnaVXm+SiOMk8AFUlPFW/n4ZN4DGo1fQRjPfw77yJLj00CWLfwVV1DSkB+MsE/5LUc0Dsm1CHICJoNw9SsTqUpHzqN8VJyZeqdwqwuZTajd6JJk1CJI76lXTdEBVtE/e1yeC/ZHAWs+UG1sEMRvyNSeRZ7LmjRJk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=kHUR4rBF; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="kHUR4rBF" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5170D1F00898; Tue, 9 Jun 2026 14:33:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1781015626; bh=741Q+uof+wQFQ/KVIzOQr/dYcimcckvcggwLVqMRUHA=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=kHUR4rBFVL/T4vICCboCXOzze8FceQXTZiNRz6s3JJecr2Gjc5VWC7rXex5kGkMoc Yk48rvqV9UXv+9V60aig44D5VNszwAhafWcxBuj5+M2N0czUG0DExOOCYaSUMx7vpp J3GHHxhb9QlViItZPlpnAniPaf/BT7/QPDEzlFceuCZGdt5KhZOHfaqrkhzBeRhV53 8QpeXxAeahVqJiuTsEaUuO8ndu1Aee/5B39ehZ9M/Il5fHz1sF7szV7FKFcrnkUxCD ZnSxOBhaKDj4vAXzWw7LhiYT9ICmbpNc8I15bGENBjm88o49kDzL4RiVr868y6LsKC 2bgWvh2KIcuJg== Date: Tue, 9 Jun 2026 15:33:40 +0100 From: Lorenzo Stoakes To: "David Hildenbrand (Arm)" Cc: Lance Yang , akpm@linux-foundation.org, ziy@nvidia.com, baolin.wang@linux.alibaba.com, liam@infradead.org, npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com, baohua@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH mm-unstable 1/1] mm/khugepaged: fix PMD collapse swap PTE accounting Message-ID: References: <20260609120443.71864-1-lance.yang@linux.dev> <7d081256-5b30-4e3c-b948-85ba76ad0e1d@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=us-ascii Content-Disposition: inline In-Reply-To: <7d081256-5b30-4e3c-b948-85ba76ad0e1d@kernel.org> On Tue, Jun 09, 2026 at 03:16:10PM +0200, David Hildenbrand (Arm) wrote: > On 6/9/26 14:04, Lance Yang wrote: > > From: Lance Yang > > > > mthp_collapse() uses mthp_present_ptes to decide whether a range has > > enough occupied PTEs to try collapse. Swap PTEs accepted by > > collapse_scan_pmd() are counted in unmapped, but are not represented in > > mthp_present_ptes. > > > > When lower orders are enabled, collapse_scan_pmd() relaxes max_ptes_none > > so the scan can cover the whole PMD and build the bitmap. mthp_collapse() > > then checks the PMD-order candidate using the bitmap. > > > > With max_ptes_none set to 0, a range with 511 present PTEs and one swap > > PTE no longer reaches collapse_huge_page(), even though PMD collapse can > > handle swap PTEs up to max_ptes_swap. > > > > Account unmapped PTEs only for PMD order. PMD collapse supports swap PTEs > > through max_ptes_swap, while lower-order mTHP collapse does not currently > > support non-present PTEs. Keep non-present PTEs out of the lower-order > > eligibility check. > > > > Signed-off-by: Lance Yang > > --- > > Sent separately, as discussed in [1], to spell out the PMD-order swap PTE > > case. Patch [2] is still only in mm-unstable, so no Fixes: tag. > > > > [1] https://lore.kernel.org/linux-mm/CAA1CXcD7WAiA1b9GTLAuNZ+kHaFx0SzZwpBkqAZ=s+RHsTUaow@mail.gmail.com/ > > [2] https://lore.kernel.org/linux-mm/20260605161422.213817-12-npache@redhat.com/ > > > > mm/khugepaged.c | 8 ++++++++ > > 1 file changed, 8 insertions(+) > > > > diff --git a/mm/khugepaged.c b/mm/khugepaged.c > > index b12187709f6d..617bca76db49 100644 > > --- a/mm/khugepaged.c > > +++ b/mm/khugepaged.c > > @@ -1508,6 +1508,14 @@ static enum scan_result mthp_collapse(struct mm_struct *mm, > > nr_occupied_ptes = bitmap_weight_from(cc->mthp_present_ptes, offset, > > offset + nr_ptes); > > > > + /* > > + * Swap PTEs accepted during the scan are counted in @unmapped, > > + * not in the present-PTE bitmap. Account them for the PMD-order > > + * candidate. > > + */ > > + if (is_pmd_order(order)) > > + nr_occupied_ptes += unmapped; > > + > > LGTM, there is a bit of opportunity for cleanup in the future :) >From my point of view, accepting the mTHP khugepaged changes was essentially a big compromise on how much it adds to the mess of the existing code base, and AFAIC we shouldn't accept any further major changes until we actually sort this mess out :) > > Acked-by: David Hildenbrand (Arm) > > > For example, as we no longer have the VMA here, collapse_max_ptes_none is > imprecise in uffd VMAs. We might try collapsing where there sure is nothing to > collapse. > > We could likely handle the userfaultfd_armed() part easier: some indication that > we must not have any pte_none() would be sufficient. > > Also, I don't see a good reason why uffd would not be allowed to collapse with > zeropages ... it's really just about missing faults due to pte_none(). Ugh uffd. > > -- > Cheers, > > David Cheers, Lorenzo