From: Randy Dunlap <rdunlap@infradead.org> To: Tejun Heo <tj@kernel.org> 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>, Michal Hocko <mhocko@suse.cz>, 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 cgroup/for-3.16] cgroup: add documentation about unified hierarchy Date: Wed, 16 Apr 2014 13:16:18 -0700 [thread overview] Message-ID: <534EE512.5090905@infradead.org> (raw) In-Reply-To: <20140416135120.GI30990@htj.dyndns.org> On 04/16/2014 06:51 AM, Tejun Heo wrote: > Hello, > > On Tue, Apr 15, 2014 at 03:36:29PM -0700, Randy Dunlap wrote: >>> +depending on the specific controller. IOW, hierarchy may be collapsed >> >> please spell out IOW > > Updated, but is this really necessary? It depends on who your audience is. I probably think that the audience is larger than you think it is. >> I would prefer to see CPU instead of cpu (except when it refers to a >> task or function). > > cpu sometimes refer to the cpu controller. Will use CPU when it's > actually referring to the CPU. OK, thanks. -- ~Randy
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> Cc: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Serge Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>, Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>, Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>, Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>, Aristeu Rozanski <arozansk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, Daniel Borkmann <dborkman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, Thomas Graf <tgraf-G/eBtMaohhA@public.gmane.org>, Lennart Poettering <lennart-mdGvqq1h2p+GdvJs77BJ7Q@public.gmane.org>, Kay Sievers <kay-tD+1rO4QERM@public.gmane.org>, Rohit Jnagal <jnagal-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>, Brandon Philips <brandon.philips-JW9irJGTvgXQT0dZR+AlfA@public.gmane.org> Subject: Re: [PATCH cgroup/for-3.16] cgroup: add documentation about unified hierarchy Date: Wed, 16 Apr 2014 13:16:18 -0700 [thread overview] Message-ID: <534EE512.5090905@infradead.org> (raw) In-Reply-To: <20140416135120.GI30990-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org> On 04/16/2014 06:51 AM, Tejun Heo wrote: > Hello, > > On Tue, Apr 15, 2014 at 03:36:29PM -0700, Randy Dunlap wrote: >>> +depending on the specific controller. IOW, hierarchy may be collapsed >> >> please spell out IOW > > Updated, but is this really necessary? It depends on who your audience is. I probably think that the audience is larger than you think it is. >> I would prefer to see CPU instead of cpu (except when it refers to a >> task or function). > > cpu sometimes refer to the cpu controller. Will use CPU when it's > actually referring to the CPU. OK, thanks. -- ~Randy
next prev parent reply other threads:[~2014-04-16 20:16 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 [this message] 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 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=534EE512.5090905@infradead.org \ --to=rdunlap@infradead.org \ --cc=arozansk@redhat.com \ --cc=brandon.philips@coreos.com \ --cc=cgroups@vger.kernel.org \ --cc=containers@lists.linux-foundation.org \ --cc=dborkman@redhat.com \ --cc=hannes@cmpxchg.org \ --cc=jnagal@google.com \ --cc=kay@vrfy.org \ --cc=lennart@poettering.net \ --cc=linux-kernel@vger.kernel.org \ --cc=lizefan@huawei.com \ --cc=mhocko@suse.cz \ --cc=peterz@infradead.org \ --cc=serge.hallyn@ubuntu.com \ --cc=tgraf@suug.ch \ --cc=tj@kernel.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: linkBe 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.