All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>
Cc: Brandon Philips
	<brandon.philips-JW9irJGTvgXQT0dZR+AlfA@public.gmane.org>,
	containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Serge Hallyn
	<serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>,
	Kay Sievers <kay-tD+1rO4QERM@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Daniel Borkmann
	<dborkman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Lennart Poettering
	<lennart-mdGvqq1h2p+GdvJs77BJ7Q@public.gmane.org>,
	Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
	Thomas Graf <tgraf-G/eBtMaohhA@public.gmane.org>,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 cgroup/for-3.16] cgroup: add documentation about unified hierarchy
Date: Tue, 22 Apr 2014 17:14:26 -0400	[thread overview]
Message-ID: <20140422211426.GD3615@mtj.dyndns.org> (raw)
In-Reply-To: <20140422162707.GR29311-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>

Hello,

Hope you enjoyed the vacation. :)

On Tue, Apr 22, 2014 at 06:27:07PM +0200, Michal Hocko wrote:
> On Wed 16-04-14 10:52:48, Tejun Heo wrote:
> [....]
> > +The memory controller currently doesn't have a way to control what
> > +happens between internal tasks and child cgroups and the behavior is
> > +not clearly defined. 
> 
> I am not sure I understand this. Could you be more specific what exactly
> is not clearly defined?

Oh, the fact that there are no control knobs for the internal tasks,
so when there's contention involving both internal tasks and child
cgroups, how resources are distributed is implementation specific
without clearly defined rules.

Thanks.

-- 
tejun

WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: Li Zefan <lizefan@huawei.com>,
	cgroups@vger.kernel.org, containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org,
	Serge Hallyn <serge.hallyn@ubuntu.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Aristeu Rozanski <arozansk@redhat.com>,
	Daniel Borkmann <dborkman@redhat.com>,
	Thomas Graf <tgraf@suug.ch>,
	Lennart Poettering <lennart@poettering.net>,
	Kay Sievers <kay@vrfy.org>, Rohit Jnagal <jnagal@google.com>,
	Brandon Philips <brandon.philips@coreos.com>
Subject: Re: [PATCH v2 cgroup/for-3.16] cgroup: add documentation about unified hierarchy
Date: Tue, 22 Apr 2014 17:14:26 -0400	[thread overview]
Message-ID: <20140422211426.GD3615@mtj.dyndns.org> (raw)
In-Reply-To: <20140422162707.GR29311@dhcp22.suse.cz>

Hello,

Hope you enjoyed the vacation. :)

On Tue, Apr 22, 2014 at 06:27:07PM +0200, Michal Hocko wrote:
> On Wed 16-04-14 10:52:48, Tejun Heo wrote:
> [....]
> > +The memory controller currently doesn't have a way to control what
> > +happens between internal tasks and child cgroups and the behavior is
> > +not clearly defined. 
> 
> I am not sure I understand this. Could you be more specific what exactly
> is not clearly defined?

Oh, the fact that there are no control knobs for the internal tasks,
so when there's contention involving both internal tasks and child
cgroups, how resources are distributed is implementation specific
without clearly defined rules.

Thanks.

-- 
tejun

  parent reply	other threads:[~2014-04-22 21:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 22:09 [PATCH cgroup/for-3.16] cgroup: add documentation about unified hierarchy Tejun Heo
2014-04-14 22:09 ` Tejun Heo
2014-04-15 22:36 ` Randy Dunlap
2014-04-15 22:36   ` Randy Dunlap
     [not found]   ` <534DB46D.7090207-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-04-16 13:51     ` Tejun Heo
2014-04-16 13:51       ` Tejun Heo
2014-04-16 20:16       ` Randy Dunlap
2014-04-16 20:16         ` Randy Dunlap
     [not found]         ` <534EE512.5090905-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-04-17  1:41           ` Li Zefan
2014-04-17  1:41             ` Li Zefan
     [not found]       ` <20140416135120.GI30990-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2014-04-16 20:16         ` Randy Dunlap
     [not found] ` <20140414220917.GD1863-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2014-04-15 22:36   ` Randy Dunlap
2014-04-16 14:52   ` [PATCH v2 " Tejun Heo
2014-04-16 14:52     ` Tejun Heo
     [not found]     ` <20140416145248.GD1257-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2014-04-22 16:27       ` Michal Hocko
2014-04-22 16:27     ` Michal Hocko
2014-04-22 16:27       ` Michal Hocko
     [not found]       ` <20140422162707.GR29311-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2014-04-22 21:14         ` Tejun Heo [this message]
2014-04-22 21:14           ` Tejun Heo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140422211426.GD3615@mtj.dyndns.org \
    --to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=brandon.philips-JW9irJGTvgXQT0dZR+AlfA@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=dborkman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
    --cc=kay-tD+1rO4QERM@public.gmane.org \
    --cc=lennart-mdGvqq1h2p+GdvJs77BJ7Q@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
    --cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
    --cc=tgraf-G/eBtMaohhA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.