[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160715141058.GI3078@mtj.duckdns.org>
Date: Fri, 15 Jul 2016 10:10:58 -0400
From: Tejun Heo <tj@...nel.org>
To: Topi Miettinen <toiwoton@...il.com>
Cc: linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
Li Zefan <lizefan@...wei.com>,
Johannes Weiner <hannes@...xchg.org>,
Markus Elfring <elfring@...rs.sourceforge.net>,
"David S. Miller" <davem@...emloft.net>,
Nicolas Dichtel <nicolas.dichtel@...nd.com>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
"open list:CONTROL GROUP (CGROUP)" <cgroups@...r.kernel.org>
Subject: Re: [PATCH 02/14] resource limits: aggregate task highwater marks to
cgroup level
Hello, Topi.
On Fri, Jul 15, 2016 at 01:35:49PM +0300, Topi Miettinen wrote:
> Collect resource usage highwater marks of a task to cgroup
> statistics when the task exits.
I'm not sure how this makes sense. The limits are enforced and
collected per user or along the process hierarchy which can be very
different from cgroup organization. What does collecting high
watermarks from orthogonal structure, sometimes even combining
per-user numbers from different users, even mean? These are numbers
without clear semantics.
Thanks.
--
tejun
Powered by blists - more mailing lists