From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f70.google.com (mail-wm0-f70.google.com [74.125.82.70]) by kanga.kvack.org (Postfix) with ESMTP id A94C16B0390 for ; Tue, 11 Apr 2017 08:30:36 -0400 (EDT) Received: by mail-wm0-f70.google.com with SMTP id x75so4354261wma.0 for ; Tue, 11 Apr 2017 05:30:36 -0700 (PDT) Received: from mx2.suse.de (mx2.suse.de. [195.135.220.15]) by mx.google.com with ESMTPS id m70si2849002wmg.146.2017.04.11.05.30.34 for (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 11 Apr 2017 05:30:35 -0700 (PDT) Date: Tue, 11 Apr 2017 14:30:26 +0200 From: Michal Hocko Subject: Re: [PATCH 2/4] mm: memcontrol: re-use global VM event enum Message-ID: <20170411123025.GL6729@dhcp22.suse.cz> References: <20170404220148.28338-1-hannes@cmpxchg.org> <20170404220148.28338-2-hannes@cmpxchg.org> <20170407124702.GE16413@dhcp22.suse.cz> <20170410141334.GA16119@cmpxchg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170410141334.GA16119@cmpxchg.org> Sender: owner-linux-mm@kvack.org List-ID: To: Johannes Weiner Cc: Andrew Morton , Vladimir Davydov , linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-team@fb.com On Mon 10-04-17 10:13:34, Johannes Weiner wrote: > On Fri, Apr 07, 2017 at 02:47:02PM +0200, Michal Hocko wrote: > > I do agree that we should share global and memcg specific events constants > > but I am not sure we want to share all of them. Would it make sense to > > reorganize the global enum and put those that are shared to the > > beginning? We wouldn't need the memcg specific translation then. > > I'm not sure I follow. Which translation? Sorry, I should have said s@translation@filtering@ by memcg1_events* > > Anyway, two comments on the current implementation. > > > > On Tue 04-04-17 18:01:46, Johannes Weiner wrote: > > [...] > > > +/* Cgroup-specific events, on top of universal VM events */ > > > +enum memcg_event_item { > > > + MEMCG_LOW = NR_VM_EVENT_ITEMS, > > > + MEMCG_HIGH, > > > + MEMCG_MAX, > > > + MEMCG_OOM, > > > + MEMCG_NR_EVENTS, > > > +}; > > > > The above should mention that each supported global VM event should > > provide the corresponding translation > > > > [...] > > > > here... > > > +/* Universal VM events cgroup1 shows, original sort order */ > > > +unsigned int memcg1_events[] = { > > > + PGPGIN, > > > + PGPGOUT, > > > + PGFAULT, > > > + PGMAJFAULT, > > > +}; > > > + > > > +static const char *const memcg1_event_names[] = { > > > + "pgpgin", > > > + "pgpgout", > > > + "pgfault", > > > + "pgmajfault", > > > +}; > > > > the naming doesn't make it easier to undestand why we need this. > > global2memcg_event? > > This is just to keep the file order consistent. It could have been > done like memory.stat in cgroup2, where we simply do > > seq_printf(s, "pgmajfault %lu\n", stat[PGMAJFAULT]); > > but I didn't want to change the v1 code too much. So these two arrays > are just a sorted list of global VM events shown in v1's memory.stat. You would still have to know which are the relevant parts of the global starts that we account for memcg. -- Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org