From: Paul Jackson <pj@sgi.com>
To: menage@google.com
Cc: akpm@linux-foundation.org, dev@sw.ru, xemul@sw.ru,
serue@us.ibm.com, vatsa@in.ibm.com, ebiederm@xmission.com,
haveblue@us.ibm.com, svaidy@linux.vnet.ibm.com,
balbir@in.ibm.com, ckrm-tech@lists.sourceforge.net,
linux-kernel@vger.kernel.org, rohitseth@google.com,
mbligh@google.com, containers@lists.osdl.org, devel@openvz.org
Subject: Re: [PATCH 0/9] Containers (V9): Generic Process Containers
Date: Sat, 28 Apr 2007 18:47:44 -0700 [thread overview]
Message-ID: <20070428184744.bc0345a0.pj@sgi.com> (raw)
In-Reply-To: <20070427104607.252541000@menage.corp.google.com>
> - decide whether "Containers" is an acceptable name for the system
> given its usage by some other development groups, or whether something
> else (ProcessSets? ResourceGroups? TaskGroups?) would be better
I place in nomination:
tasksets
However this would conflict with the taskset utility in Robert Loves
schedutils package. The 'taskset' command "is used to set or retrieve
the CPU affinity of a running process given its PID or to launch a new
COMMAND with a given CPU affinity."
The various alternatives you listed all have the advantage of stating
both that we have a container/group/set/collection/... of something,
and -what- that something might be - process/resource/task/...
"tasksets" is the shortest spelling I could think of for such a compond
"Something-Collection" form.
If the conflict with the schedutils utility is a concern, then the
next best alternative would be:
taskgroups
This is the next shortest way to spell this "Something-Collection" form.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2007-04-29 1:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 10:46 [PATCH 0/9] Containers (V9): Generic Process Containers menage
2007-04-27 10:46 ` [PATCH 1/9] Containers (V9): Basic container framework menage
2007-04-29 3:12 ` [ckrm-tech] " Paul Jackson
2007-05-01 17:40 ` Balbir Singh
2007-05-01 17:46 ` Paul Menage
2007-05-01 18:40 ` [ckrm-tech] " Paul Jackson
2007-05-02 3:44 ` Balbir Singh
2007-05-02 6:12 ` Paul Jackson
2007-05-10 4:09 ` Balbir Singh
2007-05-10 4:47 ` Paul Jackson
2007-05-10 4:49 ` Balbir Singh
2007-04-27 10:46 ` [PATCH 2/9] Containers (V9): Example CPU accounting subsystem menage
2007-05-01 17:52 ` Balbir Singh
2007-04-27 10:46 ` [PATCH 3/9] Containers (V9): Add tasks file interface menage
2007-05-01 18:12 ` Balbir Singh
2007-05-01 20:37 ` [ckrm-tech] " Paul Menage
2007-05-02 3:25 ` Srivatsa Vaddagiri
2007-05-02 3:25 ` Paul Menage
2007-05-02 3:46 ` Srivatsa Vaddagiri
2007-05-08 14:51 ` Balbir Singh
2007-05-10 21:21 ` Paul Menage
2007-05-11 2:31 ` Balbir Singh
2007-05-02 3:58 ` Balbir Singh
2007-04-27 10:46 ` [PATCH 4/9] Containers (V9): Add fork/exit hooks menage
2007-04-27 10:46 ` [PATCH 5/9] Containers (V9): Add container_clone() interface menage
2007-04-27 10:46 ` [PATCH 6/9] Containers (V9): Add procfs interface menage
2007-04-27 10:46 ` [PATCH 7/9] Containers (V9): Make cpusets a client of containers menage
2007-04-27 10:46 ` [PATCH 8/9] Containers (V9): Share css_group arrays between tasks with same container memberships menage
2007-04-27 10:46 ` [PATCH 9/9] Containers (V9): Simple debug info subsystem menage
2007-04-29 1:47 ` Paul Jackson [this message]
2007-04-29 9:37 ` [PATCH 0/9] Containers (V9): Generic Process Containers Paul Jackson
2007-04-30 17:12 ` Srivatsa Vaddagiri
2007-04-30 17:09 ` Paul Menage
2007-04-30 18:06 ` Srivatsa Vaddagiri
2007-04-30 17:23 ` Christoph Hellwig
2007-04-30 18:16 ` [ckrm-tech] " Srivatsa Vaddagiri
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=20070428184744.bc0345a0.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=containers@lists.osdl.org \
--cc=dev@sw.ru \
--cc=devel@openvz.org \
--cc=ebiederm@xmission.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=menage@google.com \
--cc=rohitseth@google.com \
--cc=serue@us.ibm.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=vatsa@in.ibm.com \
--cc=xemul@sw.ru \
/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.