From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-172.mta0.migadu.com (out-172.mta0.migadu.com [91.218.175.172]) (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 0ECE912E52 for ; Wed, 20 Mar 2024 22:36:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1710974185; cv=none; b=eLMaKnUeQWdLoRLJlmAlCTUGTq0pqpyyjmouFFW+564mcmUgXdneBMSmLlhzED8M7idXl4Pe2rC1JeBzSgEKe5AXISImPQ2vHRK+fdrCT4dPZsIWxl1mXU0br6TY4Uv3Ykmyd+3+y1p7H6ABXEWSRLo7M41uwSQBIaGVHDG7JEE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1710974185; c=relaxed/simple; bh=w4+WlveuzgqPZikAmvyx2NEP17PqNOHdzBDbDqmano0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=JuF4PCSdjpFKfRDCLB29j1skWIFCzmCK1E8sehfelA3WndQ2W9DGbPlSO0ECk59wXbZoDudfeucEXQsULVsjq3x1EQ7zxy4YvTfcXr7VaaeRfJp5XYka5wq9bmTB1d6axbsnT3VF1vc/zMo8h5bL0PdmYCINTtYZPsnhne2qPAc= 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=FMMXw7e8; arc=none smtp.client-ip=91.218.175.172 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="FMMXw7e8" Date: Wed, 20 Mar 2024 15:36:14 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1710974178; 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: in-reply-to:in-reply-to:references:references; bh=w4+WlveuzgqPZikAmvyx2NEP17PqNOHdzBDbDqmano0=; b=FMMXw7e8c2juESOCHR7WKcGaCYyV/ITXLNsnQa0XTJbQnxl2TkHAUJeu2ligkjUQ3RwMeS YlqqsGfVch8wvfdBsjZm9OMOMD9AYqssFNi/JdT6S+CInwnJofJDTQ/9a4AP5DXALmCE2m 3DGM91uQKYDj4yFkIDNpnsXz49ecDhg= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Roman Gushchin To: Johannes Weiner Cc: Andrew Morton , Michal Hocko , Shakeel Butt , Muchun Song , linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm: remove CONFIG_MEMCG_KMEM Message-ID: References: <20240320202745.740843-1-hannes@cmpxchg.org> Precedence: bulk X-Mailing-List: cgroups@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: <20240320202745.740843-1-hannes@cmpxchg.org> X-Migadu-Flow: FLOW_OUT On Wed, Mar 20, 2024 at 04:27:45PM -0400, Johannes Weiner wrote: > CONFIG_MEMCG_KMEM used to be a user-visible option for whether slab > tracking is enabled. It has been default-enabled and equivalent to > CONFIG_MEMCG for almost a decade. We've only grown more kernel memory > accounting sites since, and there is no imaginable cgroup usecase > going forward that wants to track user pages but not the multitude of > user-drivable kernel allocations. I totally support it. I believe one of the reasons for it to exist was SLOB, which hasn't been supporting the slab memory accounting. No such reasons anymore. Acked-by: Roman Gushchin Thanks!