Hi,
On Tue, May 29, 2007 at 06:01:05AM -0700, [EMAIL PROTECTED] wrote:
> +1.5 How do I use containers ?
> +--
> +
> +To start a new job that is to be contained within a container, using
> +the "cpuset" container subsystem, the steps are something like:
> +
> + 1) mkdir /dev
On Wed, 30 May 2007 07:02:00 -0700 "Paul Menage" <[EMAIL PROTECTED]> wrote:
>
> >
> > People have hit unpleasant problems before now running iput() against
> > partially-constructed inodes.
>
> What kinds of problems? Are there bits of state that I should fully
> construct even if I'm going to i
On 5/30/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
Holy cow, do we need all those?
I'll experiment to see which ones we can get rid of.
> +typedef enum {
> + CONT_REMOVED,
> +} container_flagbits_t;
typedefs are verboten. Fortunately this one is never referred to - only
the values a
On Tue, 29 May 2007 06:01:05 -0700 [EMAIL PROTECTED] wrote:
> This patch adds the main containers framework - the container
> filesystem, and the basic structures for tracking membership and
> associating subsystem state objects to tasks.
>
> ...
>
> --- /dev/null
> +++ container-2.6.22-rc2-mm1/i
On Tue, 29 May 2007 06:01:05 -0700 [EMAIL PROTECTED] wrote:
> +For example, the following sequence of commands will setup a container
> +named "Charlie", containing just CPUs 2 and 3, and Memory Node 1,
> +and then start a subshell 'sh' in that container:
> +
> + mount -t container cpuset -ocpuse
5 matches
Mail list logo
