All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: Sam Vilain <sam@vilain.net>
Cc: Dave Hansen <haveblue@us.ibm.com>,
	linux-kernel@vger.kernel.org,
	Herbert Poetzl <herbert@13thfloor.at>,
	"Eric W.Biederman" <ebiederm@xmission.com>,
	OpenVZ developers list <devel@openvz.org>,
	"Serge E.Hallyn" <serue@us.ibm.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] [PATCH 0/7] Some basic vserver infrastructure
Date: Wed, 22 Mar 2006 17:18:04 +1200	[thread overview]
Message-ID: <4420DE0C.3080300@vilain.net> (raw)
In-Reply-To: <4420885F.5070602@vilain.net>

Sam Vilain wrote:

>Using the term "task_ns" and ID term "nsid":
>
>  CONFIG_TASK_NS - config option
>  typedef unsigned int nsid_t;
>  struct task_ns
>  task_struct->task_ns
>  task_struct->nsid
>  task_nsid(struct task*) - get an NSID from a task_struct
>  current_nsid - get NSID for current
>  task_ns_state(struct task_ns*, TASK_NS_STATE_FOO) - does task_ns hav...
>  create_task_ns - creates a new context and "hashes" it
>  lookup_task_ns - lookup a task_ns by nsid
>  get_task_ns - increase refcount of a task_ns
>     [...]
>  release_task_ns - decrease the process count for a task_ns
>  task_get_task_ns - like get_task_ns, but by process
>  task_ns_migrate_task - join task to a task_ns
>  task_ns_printk - debugging printk (for CONFIG_TASK_NS_DEBUG)
>  task_ns_hist_alloc_task_ns - history tracing (for CONFIG_TASK_NS_HI...
>  constants:
>     TASK_NS_STATE_FOO - state bits
>     TASK_NS_FLAG_FOO - task_ns flags (to select features)
>     TASK_NS_CAP_FOO - task_ns-specific capabilities
>     TASK_NS_CMD_get_version - task_ns subcommand names
>     TASK_NS_VCI_VERSION
>  
>

One more (apparently suggested by Eric Biederman, though perhaps he had
different ideas about what it would look like)

  CONFIG_SPACE - config option
  typedef unsigned int space_t;
  struct space_info;
  task_struct->space
  task_struct->space_id
  task_space_id(struct task*) - get an SPACE_ID from a task_struct
  current_space_id - get SPACE_ID for current
  space_info_state(struct space_info*, TASK_SPACE_STATE_FOO) - does ...
  create_space - creates a new space and "hashes" it
  lookup_space - lookup a space_info by space_id
  get_space_info - increase refcount of a space_info
  put_space_info - decrease refcount of a space_info
     [...]
  grab_space - increase the process count for a space
  release_space - decrease the process count for a space
  task_get_space_info - like get_space_info, but by process
  space_migrate_task - join task to a space
  space_printk - debugging printk (for CONFIG_SPACE_DEBUG)
  space_hist_alloc_space - history tracing (for CONFIG_SPACE_HI...
  constants:
     SPACE_STATE_FOO - state bits
     SPACE_FLAG_FOO - task_ns flags (to select features)
     SPACE_CAP_FOO - task_ns-specific capabilities
     SPACE_CMD_get_version - task_ns subcommand names
     SPACE_SYSCALL_VERSION


Something like that, anyway.  I must admit "Task Spaces" sounds a little
less dorky than "Task Namespaces", but doesn't roll off the tongue that
well because of the '-sk s..' combination.

Anyone?

Sam.

  reply	other threads:[~2006-03-22  5:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060321061333.27638.63963.stgit@localhost.localdomain>
2006-03-21 18:50 ` [RFC] [PATCH 0/7] Some basic vserver infrastructure Dave Hansen
2006-03-21 21:08   ` Sam Vilain
2006-03-21 21:32     ` Dave Hansen
2006-03-21 23:12       ` Sam Vilain
2006-03-22  5:18         ` Sam Vilain [this message]
2006-03-22  7:13         ` Eric W. Biederman
2006-03-23  4:17           ` Sam Vilain
2006-03-24 15:36           ` [Devel] " Kirill Korotaev
2006-03-27 12:45             ` Serge E. Hallyn
2006-03-28  5:28               ` Sam Vilain
2006-03-29 12:07               ` Kirill Korotaev
2006-03-29 13:47                 ` Serge E. Hallyn
2006-03-29 21:30                   ` Sam Vilain
2006-04-19  7:50                     ` Eric W. Biederman
2006-04-19 21:42                       ` Sam Vilain
2006-03-22  6:41   ` Eric W. Biederman
2006-03-23  4:29     ` Sam Vilain
2006-03-23  4:50       ` Andrew Morton
2006-03-24 15:38       ` Kirill Korotaev
2006-03-24 15:37     ` Kirill Korotaev
2006-03-24 20:28       ` Eric W. Biederman
2006-03-24 21:01         ` Herbert Poetzl
2006-03-24 21:13           ` Eric W. Biederman
2006-03-24 21:40             ` Herbert Poetzl
2006-03-24 22:30               ` Eric W. Biederman
2006-03-25 18:37                 ` Eric W. Biederman
     [not found] ` <20060321061333.27638.9112.stgit@localhost.localdomain>
2006-03-21 18:53   ` [RFC] [PATCH 1/7] Add process virtualisation umbrella structure (vx_info) Dave Hansen
2006-03-21 21:52     ` Sam Vilain
2006-03-22  2:02     ` Herbert Poetzl

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=4420DE0C.3080300@vilain.net \
    --to=sam@vilain.net \
    --cc=akpm@osdl.org \
    --cc=devel@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=haveblue@us.ibm.com \
    --cc=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    /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.