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 22990420485 for ; Thu, 6 Aug 2026 09:48:58 +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=1786009739; cv=none; b=ECBYdVVD2ZmSTp1J2AGwTiPobtrlZmnpIr5ezfBBI2mFQclNVzJbT+iWtYl8mqWmstb9aZEA6ZAXbBKCSOs4+c9hl57yoEUR/uMoKZc3dh/W0BUnAkLL0qA496rrdTpnDxPLcQsq1zsA7G3BZIdvocKC5GQV2iXWqHTau2LKeCs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786009739; c=relaxed/simple; bh=zaAAeEbwqzKwToy90LuzRfiT0XS68eqv5FapbEIYz4E=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=sBDqvvQyJuRbzB/GF1z9HVJs6JNOStnDZqKWdXufWXr8jzjrkNN3MjFa1UQUK7mdavEHqrUd3VtzpvXG8AwISbbb+SsWpuMocowZa79XO8v2XLl7aMU/rE3EkRRpYR/dvPRBGTEjlzNTh81ShkjUoWIlQb3qSFx6yUW7xBhvwwI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=H1M6zHDY; 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="H1M6zHDY" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3E4C31F000E9; Thu, 6 Aug 2026 09:48:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1786009738; bh=zaAAeEbwqzKwToy90LuzRfiT0XS68eqv5FapbEIYz4E=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=H1M6zHDY7xKJ6TiAV/oLvwqhETK5AzX+0vWa8UnUQuFRXz4mXn98+RMq/TtJCCffJ p/baFnXOL+1ZdBET2YZ53PL6MIZCijoNGq7xv2oYU/PL3L0HIu3y6jClOgOcsVkVcf mby2UcjM0JDXqugvBtHv2tnzE30sShNr7pol4xQn1f2GBTHjNR/Y6kFPUKQ71OMv+8 CXAV0pUwcKSiBmpUSs4KwamCMs5Mp41rhBInVa4aJkWcpy7egqASOLKiXruSj/6Oet 8z00rIo6NpGTeXkw/SmuHqDm62zSehwdp3deWGr3UhHVfwMcx8DsNDEejqcmoR8b3x LZ0zEMUwuLprw== Date: Thu, 6 Aug 2026 10:48:39 +0100 From: "Lorenzo Stoakes (ARM)" To: Juan Yescas Cc: Andrew Morton , David Hildenbrand , Lorenzo Stoakes , "Liam R. Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , open list , "open list:MEMORY MANAGEMENT - CORE" , android-mm@google.com, fvdl@google.com, tkjos@google.com, minchan@google.com, dskiba@google.com Subject: Re: [RFC PATCH v2 00/16] Page Alloc Hogger Message-ID: References: <20260806011048.517229-1-jyescas@google.com> 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: <20260806011048.517229-1-jyescas@google.com> Hi Juan, While I think there's possibly value in people not re-implemented their own allocation injector, I don't think there's value in having this be part of core-mm. I really don't want this to form part of any contract or to be blessed in any way by core mm as it exposes internal implementation details and I really want to avoid adding extra maintainer workload here. I'd suggest keeping it as an out-of-tree module as David proposed previously ([0]). Alternatively, keeping it as part of tooling (e.g. in tools/testing) could also work. (This is no comment on how useful it might be for debugging or testing scenarios :) -- Cheers, Lorenzo [0]:https://lore.kernel.org/all/97605949-82c5-49e0-84b6-b42e8078b55d@kernel.org/