From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3C147C282CE for ; Wed, 10 Apr 2019 19:54:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 028C92133D for ; Wed, 10 Apr 2019 19:54:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1554926092; bh=VCdmMJ9sZIVBV6R1GcL/BWaj++yiLYTZXs7qXFRNje0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=fssy7znpIwwHEC3Bai5TMfqxhqkKw8v0mKMO/GdPXI6XgtYLrrmvDexBuZDd4thcE 8WwP0jVqZ5f82X1GMQXCayhzhWPxfaYdM+hjqtrJ0BG9SJS/b3mdZqt3k1sdhM1LGX UtLdBKeZpJHDbCjabPo+f1R+uzjvWn9IBYBZoFAA= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726766AbfDJTyv (ORCPT ); Wed, 10 Apr 2019 15:54:51 -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