From: Paul Jackson <pj@sgi.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: xpl@amln.net, menage@google.com, containers@lists.osdl.org,
linux-kernel@vger.kernel.org, balbir@linux.vnet.ibm.com,
a.p.zijlstra@chello.nl, xemul@openvz.org,
akpm@linux-foundation.org
Subject: Re: [RFC] Prefixing cgroup generic control filenames with "cgroup."
Date: Tue, 4 Mar 2008 19:24:36 -0600 [thread overview]
Message-ID: <20080304192436.5690bc0e.pj@sgi.com> (raw)
In-Reply-To: <47CBA787.8020100@cn.fujitsu.com>
Paul M wrote (quoted by Li Zefan):
>> A compromise might be to keep "tasks" unprefixed, and say that future
>> names get the "cgroup." prefix;
Another stray idea, for the master of stray ideas ;), how about (1) renaming
all the cgroup files as you like, Paul M, even including tasks to cgroup.tasks
or whatever, and then (2) adding symlinks for the legacy names, such as:
tasks -> cgroup.tasks
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
prev parent reply other threads:[~2008-03-05 1:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 21:14 [RFC] Prefixing cgroup generic control filenames with "cgroup." Paul Menage
2008-02-28 21:21 ` Andrew Morton
2008-02-28 21:28 ` Paul Menage
2008-02-28 21:33 ` serge
2008-02-28 22:06 ` Paul Menage
2008-03-03 8:38 ` Paul Menage
2008-03-03 9:59 ` Balbir Singh
2008-02-28 21:40 ` Andrew Morton
2008-02-28 22:06 ` Paul Menage
2008-02-28 22:21 ` Andrew Morton
2008-02-28 22:26 ` Paul Menage
2008-02-29 5:59 ` [RFC] [PATCH] " Paul Menage
2008-02-29 6:20 ` Paul Jackson
2008-02-29 9:34 ` Paul Menage
2008-02-29 15:30 ` Paul Jackson
2008-02-29 17:59 ` Paul Menage
2008-02-29 19:20 ` Paul Jackson
2008-02-28 21:28 ` [RFC] " serge
2008-02-28 23:36 ` Paul Jackson
2008-02-29 1:03 ` Paul Menage
2008-02-29 1:22 ` Paul Jackson
2008-02-29 11:38 ` Xpl++
2008-03-03 7:23 ` Li Zefan
2008-03-03 9:11 ` Paul Menage
2008-03-05 1:24 ` Paul Jackson [this message]
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=20080304192436.5690bc0e.pj@sgi.com \
--to=pj@sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=xemul@openvz.org \
--cc=xpl@amln.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox