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 125F2238C1B for ; Thu, 18 Dec 2025 09:33:20 +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=1766050401; cv=none; b=mHa40GGUG1ikPtoBG8AjL4Xbsja8LaoRmLlUzTSOn6RBWs26k5ADOTCBlvI+sYiMWUmt/btOvnkUwfG58CGzucOWaYvIZcsQ/SUZjGwfr8/PhX6VC+G4iWmqg1GbyAlkTYQZlQ1RDaSxZyr9aqm8rPxRW9heg5OlDrizc0FeYHE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766050401; c=relaxed/simple; bh=L8BJRVo1tLN2SwwHEUQ2duZ+GDJlKDOk1B9Tn8CK80Y=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=cXmLATyI4ZEzqQ8EO26+3x1+mlmxihEO1d3ZTbtLf0buMB+mRhwEXAr8omEowhIbuljz2iAqNHCiVNvLnXPreXCnmzp2RaFTbegFpB7yY5WLzC4OI+33Em7hEOuhIFHGYbkpqGMrJhEXbgcCf1Mc2ybOGo7zPpY2UqdQJ0pWn/c= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=oE3IuCqK; 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="oE3IuCqK" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4E183C4CEFB; Thu, 18 Dec 2025 09:33:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1766050400; bh=L8BJRVo1tLN2SwwHEUQ2duZ+GDJlKDOk1B9Tn8CK80Y=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=oE3IuCqKlINhrjN+LbsSoFCb4Fk6JTMP3JgEpmraKrWva7NphDNjskczSajTGp3Ap rgKU9CRcmqVwfBciC5u4L6LMEnsq0Q4CnnpLBzevTJomAG945kJUkP4jRys9399GqT WYYPmW/UKoK5iz4E7ahj0eHx19NmMXjsQTZqzR1QdZYy8eQJnQSoMvaqnIQ04R5wrd TG+m4InTLhOtUn0l06CWiBCGiHp+7h6VHjmeV5CY65sR4eXAYoMtcYFhe9feK8KiXB LEK3QkwBRwCHyE/LcnOc7IVhPLpXSn1sUAaqS64+xfc+dqh1iMc+SIXEMYau8fup3j myWaBWCkb1sLQ== Message-ID: <11025f1c-88d3-41a9-8290-21a9565e9bc3@kernel.org> Date: Thu, 18 Dec 2025 10:33:16 +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 4/4] mm: khugepaged: set to next mm direct when mm has MMF_DISABLE_THP_COMPLETELY To: Vernon Yang , akpm@linux-foundation.org, lorenzo.stoakes@oracle.com Cc: ziy@nvidia.com, npache@redhat.com, baohua@kernel.org, lance.yang@linux.dev, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Vernon Yang References: <20251215090419.174418-1-yanglincheng@kylinos.cn> <20251215090419.174418-5-yanglincheng@kylinos.cn> From: "David Hildenbrand (Red Hat)" Content-Language: en-US In-Reply-To: <20251215090419.174418-5-yanglincheng@kylinos.cn> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 12/15/25 10:04, Vernon Yang wrote: > When an mm with the MMF_DISABLE_THP_COMPLETELY flag is detected during > scanning, directly set khugepaged_scan.mm_slot to the next mm_slot, > reduce redundant operation. That conceptually makes sense to me. How much does that safe in practice? Do you have some performance numbers for processes with rather large number of VMAs? -- Cheers David