Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4747359imu; Tue, 29 Jan 2019 06:55:02 -0800 (PST) X-Google-Smtp-Source: ALg8bN73jX/xis6ipFJkfMAZIaA+ng2FNZbu+3PiB9OajTurvxLiTzlmLvZOoRYbQ6ZcDVlXNYON X-Received: by 2002:a63:2054:: with SMTP id r20mr23712795pgm.328.1548773702092; Tue, 29 Jan 2019 06:55:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548773702; cv=none; d=google.com; s=arc-20160816; b=MMuu29j6dBiFiVjbyrNU1EjY1yWCjuLLxYkPfTKxS4mA0enOFMCIuJkivhxCHNORyM EkyotxCAYsZ78Sj1oIMXMJUF5/ONAFzc8nSnvz+9ncJCnJcMq82gUkj/Y2iOaNcEJrS7 sHnU/+6YZfit1QSQy6fnEX2QqLBbE7v0ijJq3bskAJo0SzHC/ppO5xTw3Aub5ebAbkeP YDNL/IPNE17bh8KMfhH0HJC5r8wZ3rMvObCfYJ7rMoFZiHusnl83nrd820FvvPnFI9XK axXe8eFa1fCz+Qxdp6SThtjQ0NvfuM3caRsm2mBkHZW/FhYnDgD7cMNnIx93bvkK+lV6 WNjA== 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:dkim-signature; bh=zQdBRqPFHOQNaO1SDGHuI8AHS8ubhF0Kp7ZKbPRa6WM=; b=n05agnCc+GSrV1EYWv/VmcRkGjqIQ8rqQrCY6Gn+12DJjDNLXIIIBiQtzvWCCdOict jJzD246IeWnAOKLkCRTqHAPc+fQqPzQc89XPXe3g2GjMQYodurDiiVyz5OJd2yOk5ud7 iFnZEP2cIEWXBIrHqN/Thm7SDRQAgujhHuwuHfJ2pn6vYpD21Ua/A0gtC4fbo/phhRc5 iJ83Isa7iJ+oHPm1c9CnOo9pQuIMkxUiVmdK7VRRcAbtpud8MRPfDo6DhZ0BnE/GNhDN 8X7mTpykBqu3Y2yDl5aQCF9Rr9ucngPExzqU0qhi+g0T0j9eJvkZ2rCVLgjWTox5UO4K 8iRQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=Dz35Rfkm; 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 j21si3174352pfn.277.2019.01.29.06.54.45; Tue, 29 Jan 2019 06:55:02 -0800 (PST) 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; dkim=fail header.i=@gmail.com header.s=20161025 header.b=Dz35Rfkm; 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 S1727857AbfA2Owq (ORCPT + 99 others); Tue, 29 Jan 2019 09:52:46 -0500 Received: from mail-yw1-f68.google.com ([209.85.161.68]:40684 "EHLO mail-yw1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725730AbfA2Owp (ORCPT ); Tue, 29 Jan 2019 09:52:45 -0500 Received: by mail-yw1-f68.google.com with SMTP id g194so8271607ywe.7; Tue, 29 Jan 2019 06:52:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=zQdBRqPFHOQNaO1SDGHuI8AHS8ubhF0Kp7ZKbPRa6WM=; b=Dz35RfkmFlIAefYXONkJks2DWh4gCYSnDKx7Ic9HCprDFYX5Ou5vbuEIkXMn+z+fVO JlHPuKDsGHYaZ5pZSVsoIO7EAEa11SntplExSN4clqxj1CByxBGlYVrJST4PezDYw34n Vc/jMONPC/0IrDFDJG3YbY7XtYxPITE6fLy2D7OpGo1S1N/Z/E02SXKASbQoaIFKVk7G gBWy0pe9nZYbE5UcQFeAvBwRLg+/EDPeW4VWsHdPRYpsNKmZdE398QzmsTJKW9nGvl+i 92Mpet2l+ATxjKuy62Xea++iKrZ7k8T3k3Rk3Aj5HsH1IS3R+V/R7YoWg5HgP5Pd274u s6Yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=zQdBRqPFHOQNaO1SDGHuI8AHS8ubhF0Kp7ZKbPRa6WM=; b=FTHzog2ib7550f0duCHqT+KZG9OEfq2v5eLQtz0MJUtRIT2SoanVatYepV0Lnmkce/ 5vgEF5iWP+8uBBOvAIYL5jH/CbkTfI/8MU39FwfgictCBq6laFM2bbCAdgsL+IUoK3a7 1ZEJUUwr5b8dLXPmuy3BQtVLCNAfIooQeeVoa57dub3/tlDYfow1IkjbYlLTSQl2Wqp/ 3VBaxIj5Y8XBA+DHl8PSzhlXzdf80BV93jTcNPJYeMbI1cmxAhMPdNiYiXlyH1EYDaGo d3UGW+rRVvM3JufJgJrLzJlmchw7ys0AmCUGt0oYLX6jGT5FJtAGSjnd58uC+Pj1YONI 6ebg== X-Gm-Message-State: AJcUukftVLeHku10jBZOCNU0cikwY2/h6Vd/FDHAYNZPF9Tt0GZ4XBrp b9nntRVKy130DRRk+0QV9Tc= X-Received: by 2002:a81:8a07:: with SMTP id a7mr24626349ywg.403.1548773564329; Tue, 29 Jan 2019 06:52:44 -0800 (PST) Received: from localhost ([2620:10d:c091:200::7:19ad]) by smtp.gmail.com with ESMTPSA id d4sm13949191ywe.104.2019.01.29.06.52.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Jan 2019 06:52:43 -0800 (PST) Date: Tue, 29 Jan 2019 06:52:40 -0800 From: Tejun Heo To: Michal Hocko Cc: Johannes Weiner , Chris Down , Andrew Morton , Roman Gushchin , Dennis Zhou , linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-mm@kvack.org, kernel-team@fb.com Subject: Re: [PATCH 2/2] mm: Consider subtrees in memory.events Message-ID: <20190129145240.GX50184@devbig004.ftw2.facebook.com> References: <20190125182808.GL50184@devbig004.ftw2.facebook.com> <20190128125151.GI18811@dhcp22.suse.cz> <20190128142816.GM50184@devbig004.ftw2.facebook.com> <20190128145210.GM18811@dhcp22.suse.cz> <20190128145407.GP50184@devbig004.ftw2.facebook.com> <20190128151859.GO18811@dhcp22.suse.cz> <20190128154150.GQ50184@devbig004.ftw2.facebook.com> <20190128170526.GQ18811@dhcp22.suse.cz> <20190128174905.GU50184@devbig004.ftw2.facebook.com> <20190129144306.GO18811@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190129144306.GO18811@dhcp22.suse.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Tue, Jan 29, 2019 at 03:43:06PM +0100, Michal Hocko wrote: > All memcg events are represented non-hierarchical AFAICS > memcg_memory_event() simply accounts at the level when it happens. Or do > I miss something? Or are you talking about .events files for other > controllers? Yeah, cgroup.events and .stat files as some of the local stats would be useful too, so if we don't flip memory.events we'll end up with sth like cgroup.events.local, memory.events.tree and memory.stats.local, which is gonna be hilarious. If you aren't willing to change your mind, the only option seems to be introducing a mount option to gate the flip and additions of local files. Most likely, userspace will enable the option by default everywhere, so the end result will be exactly the same but I guess it'll better address your concern. Thanks. -- tejun