From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-173.mta0.migadu.com (out-173.mta0.migadu.com [91.218.175.173]) (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 9C2C8388E72 for ; Sat, 13 Jun 2026 04:22:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.173 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781324587; cv=none; b=fOyEYx3YX0ZG4x3/19k6pq2/eNkYYfd92Jz4VjhCeod6gelBjKse1FSbjSHTfNJnpnoUvnB5jP2zgvCMMv/W4l7CFznhDOxP89IEysvU5YIwMJ6E4E6i7tj8V+zp9CCX21hBz7mQoWuW8GuumQJ4EaTttnhlzM2owjX3KZqefFs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781324587; c=relaxed/simple; bh=7azSf0ojFbg4BslySgB193eAhR97xHXrToYECSlqs5c=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version:Content-Type; b=WVwwbYFg7ycHtue/YIjBZLtzD7sFFbBMY/r+TIPqUU/Be0qMDJUMCo2E6s0PdbudSGiuhad9t+dkJo/IfvYwZLDvN10OYcMcb1Ru6zNSdgp4FAihXf2ouSffWgI62Li04gA1ayXnqEw1BDH16sYKooNaHu3CPmYv47gLBBV2NYc= 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=tPb/kuJv; arc=none smtp.client-ip=91.218.175.173 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="tPb/kuJv" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1781324576; 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=DEMwa4f1MFnoeLMMYpMgo/qvtlYKFkI0l0gCAFNfcMQ=; b=tPb/kuJvWgaPzvQpy+4bzGMmKA8DJRnuluujcznryfkSdJX4r649PfcIlHlywiFQYv2cBu fmtO8tEOi8UZ3flArfYAvge816lR4fX9d07VP4xxMsfg0sHnRtmOggt8xINgnWQbWc0RdR AVru2TvWh3ebEYv2mgiG7T8fnKxfOaQ= From: Lance Yang To: usama.arif@linux.dev Cc: david@kernel.org, lance.yang@linux.dev, ying.huang@linux.alibaba.com, baoquan.he@linux.dev, willy@infradead.org, youngjun.park@lge.com, hannes@cmpxchg.org, riel@surriel.com, ljs@kernel.org, shakeel.butt@linux.dev, alex@ghiti.fr, kas@kernel.org, baohua@kernel.org, dev.jain@arm.com, baolin.wang@linux.alibaba.com, npache@redhat.com, linux-mm@kvack.org, akpm@linux-foundation.org, liam@infradead.org, ryan.roberts@arm.com, chrisl@kernel.org, vbabka@kernel.org, linux-kernel@vger.kernel.org, nphamcs@gmail.com, shikemeng@huaweicloud.com, kernel-team@meta.com, kasong@tencent.com, ziy@nvidia.com Subject: Re: [v2 00/16] mm: PMD-level swap entries for anonymous THPs Date: Sat, 13 Jun 2026 12:22:32 +0800 Message-Id: <20260613042232.93691-1-lance.yang@linux.dev> In-Reply-To: <680441bf-c878-4a00-8787-63ad8b201bc9@linux.dev> References: <680441bf-c878-4a00-8787-63ad8b201bc9@linux.dev> 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-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT On Wed, Jun 10, 2026 at 03:44:32PM +0100, Usama Arif wrote: > > >On 10/06/2026 14:48, David Hildenbrand (Arm) wrote: >> On 6/10/26 15:01, Lance Yang wrote: >>> >>> >>> On 2026/6/10 20:24, David Hildenbrand (Arm) wrote: >>>> On 6/9/26 16:29, Usama Arif wrote: >>>>> >>>>> >>>>> >>>>> Hello! >>>>> >>>>> Just following up if there were any reviews/comments on this series! >>>>> >>>>> I know its a large series but was just checking if there was any >>>>> feedback? >>>> >>>> It shall be reviewed. We just finished the mTHP khugepaged review to get it into >>>> 7.2, so we've all been rather busy. >>> >>> Right, mTHP khugepaged was a rough one. Glad we got it over the line, >>> but yeah, there's just been a lot of THP work lately. pretty nonstop ... >>> > >Yeah its definitely a lot. I have set a target of leaving review comments on >atleast 2 patches from mm per day myself, but even that can sometimes be >difficult! I will try and help out more in reviews. Awesome! >>>> (I mean, just take a look at the THP-related flood of patches we are fighting >>>> with on a daily basis, it's not funny anymore) >>>> >>>> This is clearly going to be 7.3 material, so there is plenty of time given that >>>> the merge window is about to open soon. >>> >>> Usama, I'll try to make this one a priority too. Looks interesting :P > >Thanks Lance! > >> >> I have two other bigger series to review, but I should soon get to this as well. >> > >No worries at all! Thanks for the reviews! and yeah definitely 7.3. > >I will send this out again when 7.3-rc1 opens (rebased), so that the reviews wont be on >outdated code which could cause some confusion. After skimming through the whole series, probably PMD swap entries need one bigger rethink ... Emm ... same tricky bit keeps showing up ... One PMD swap entry is easy to handle while the swapcache still has one PMD-sized folio behind it. Once taht folio got split and reclaimed, the 512 swap slots need per-page handling :) Maybe worth first pinning down the rule here. Is a PMD swap entry supposed to mean "there is, or soon will be, one PMD- sized folio behnid it", or is just a compact page-table encoding for 512 swap slot? Without that rule being very clear, every caller has to guess how much it can assume, and it is easy to miss one ... So I stopped staring at the details for now, because the same issue keeps popping up wearing a slightly different hat :) Anyway, no clever answer from me here, not a swap expect :( Just pointing out the pattern I keep runing into. Thanks, Lance