Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5168897yba; Wed, 10 Apr 2019 12:57:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqzqwvXX/pnbAkWGzlfDyzaQyWQn8jdPTxddAQuQI0e2yP30Yb650iRVmT8aAgxtyHRHbDv1 X-Received: by 2002:a62:b61a:: with SMTP id j26mr45788680pff.203.1554926227859; Wed, 10 Apr 2019 12:57:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554926227; cv=none; d=google.com; s=arc-20160816; b=lP+t/DM9SP1tGnvjeoBaWWUtL0g3KPImnT93XdxeuPZMBsKox2Dk0GNyDHvADK2+uy 9BqiuOb9FjWCJe0y9ZpPGzaemz9Bltt2NwN3/63J4pyxsyPJUyqZtHV10BBXwYCrskjI nqXKlOBNpS+MABduPVwbDz1Nhr1URIbhDmh9OhU6LlsKQtAhfpeffZJe378hJmljBiw0 wByG+Qg40dzaNUhEfWKat8K1f0Zrx9qMpJeowYd3uBPZiv7y2/tHiuy2CuDT18urjyIm ZUNUUopYjjnxnVe80G4WDcp4tUKymC321fZ5Kbed3vLOKULbM5ERmaTtEWH8d6dg3yaV 9lZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=BEw+zpwtoGsN8GNgkVXhTtmFpQDYvQ9jV+gpZs/+t9k=; b=XQrQeXuW+xvDzxnO0nkPiRHJ+AmXnalWDYZ6OjHaosviY7n4//Ac1+teU12OKzeqm3 BZZ8KKp3RkVbeMI/JKBFu2CQjfjYZTWE0mLQHs5q2Xx1Z7vzj/ugu4dkvRouxeJhv68p pbIMqwnSHQB7lnhpasw5eOlvkNpt9mEBvmHmIpV7D0sz58GEp8spKINk/oOL+bigMywM ifz03r9Z+8WxobBX2R1icK4GOUMEAiIDxUe6Lv2CZlLClpqMl/AcAxefTStCptsb3tf5 mV6G0TH4IA4h0/rz/qvnZO6fGF6APlBsO1PlZbLbtLPgY56kH4SoreqKx617N+EFnZlj sAYg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j71si15388087pge.190.2019.04.10.12.56.51; Wed, 10 Apr 2019 12:57:07 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726752AbfDJTyu (ORCPT + 99 others); Wed, 10 Apr 2019 15:54:50 -0400 Received: from mx2.suse.de ([195.135.220.15]:47410 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726093AbfDJTyu (ORCPT ); Wed, 10 Apr 2019 15:54:50 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id EC13CAC31; Wed, 10 Apr 2019 19:54:47 +0000 (UTC) Date: Wed, 10 Apr 2019 21:54:43 +0200 From: Michal Hocko To: Waiman Long Cc: Tejun Heo , Li Zefan , Johannes Weiner , Jonathan Corbet , Vladimir Davydov , linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , Roman Gushchin , Shakeel Butt , Kirill Tkhai , Aaron Lu Subject: Re: [RFC PATCH 0/2] mm/memcontrol: Finer-grained memory control Message-ID: <20190410195443.GL10383@dhcp22.suse.cz> References: <20190410191321.9527-1-longman@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190410191321.9527-1-longman@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 10-04-19 15:13:19, Waiman Long wrote: > The current control mechanism for memory cgroup v2 lumps all the memory > together irrespective of the type of memory objects. However, there > are cases where users may have more concern about one type of memory > usage than the others. > > We have customer request to limit memory consumption on anonymous memory > only as they said the feature was available in other OSes like Solaris. Please be more specific about a usecase. > To allow finer-grained control of memory, this patchset 2 new control > knobs for memory controller: > - memory.subset.list for specifying the type of memory to be under control. > - memory.subset.high for the high limit of memory consumption of that > memory type. Please be more specific about the semantic. I am really skeptical about this feature to be honest, though. > For simplicity, the limit is not hierarchical and applies to only tasks > in the local memory cgroup. This is a no-go to begin with. > Waiman Long (2): > mm/memcontrol: Finer-grained control for subset of allocated memory > mm/memcontrol: Add a new MEMCG_SUBSET_HIGH event > > Documentation/admin-guide/cgroup-v2.rst | 35 +++++++++ > include/linux/memcontrol.h | 8 ++ > mm/memcontrol.c | 100 +++++++++++++++++++++++- > 3 files changed, 142 insertions(+), 1 deletion(-) > > -- > 2.18.1 -- Michal Hocko SUSE Labs