public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: menage@google.com
Cc: akpm@osdl.org, ckrm-tech@lists.sourceforge.net,
	mbligh@google.com, rohitseth@google.com, winget@google.com,
	dev@sw.ru, sekharan@us.ibm.com, linux-kernel@vger.kernel.org,
	jlan@sgi.com
Subject: Re: [RFC][PATCH 0/4] Generic container system
Date: Thu, 28 Sep 2006 11:49:39 -0700	[thread overview]
Message-ID: <20060928114939.d13c957b.pj@sgi.com> (raw)
In-Reply-To: <20060928104035.840699000@menage.corp.google.com>

Menage wrote:
> This patchset extracts the process grouping code from cpusets into a
> generic container system,

Interesting.  I'll try to give it a careful review in the next couple
of days.

I've added Jay Lan <jlan@sgi.com> to the cc list.  I encourage you to
include him on your cc list in the future - thanks.  He has expertise
in some of SGI's earlier container-like efforts.

> cpusets ... well documented
> (particularly with regards to synchronization rules).

thanks ;

Question (perhaps already answered in your code - I haven't looked
yet): can loadable kernel modules register containers?  I'd like to
see at least GPL modules be able to register containers, but I
appreciate that this could be a controversial issue.  Technically, I am
guessing that some EXPORT_GPL_SYMPOL declarations on the necessary
container registration routines would provide GPL modules with this
capability.

Guess I should read the code ...

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  parent reply	other threads:[~2006-09-28 18:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28 10:40 [RFC][PATCH 0/4] Generic container system menage
2006-09-28 10:40 ` [RFC][PATCH 1/4] Generic container system abstracted from cpusets code menage
2006-09-28 23:45   ` Paul Jackson
2006-10-02  6:48     ` Paul Menage
2006-10-02  8:46       ` [ckrm-tech] " Paul Jackson
2006-10-02  8:48       ` Paul Jackson
2006-09-28 10:40 ` [RFC][PATCH 2/4] Cpusets hooked into containers menage
2006-09-28 23:48   ` Paul Jackson
2006-09-28 10:40 ` [RFC][PATCH 3/4] Add generic multi-subsystem API to containers menage
2006-09-28 10:40 ` [RFC][PATCH 4/4] Simple CPU accounting container subsystem menage
2006-09-28 18:49 ` Paul Jackson [this message]
2006-09-28 19:00   ` [RFC][PATCH 0/4] Generic container system Paul Menage
2006-09-29  4:31 ` Paul Jackson
2006-09-29 15:43   ` [ckrm-tech] " Paul Menage
  -- strict thread matches above, loose matches on Subject: below --
2006-10-02  9:53 Paul Menage
2006-10-04  1:35 ` Chandra Seetharaman
2006-10-04  2:34   ` Paul Menage
2006-10-04  4:43     ` Paul Jackson
2006-10-04 18:56     ` Chandra Seetharaman
2006-10-04 19:36       ` Martin Bligh
2006-10-04 21:37         ` Chandra Seetharaman
2006-10-04 21:42           ` Paul Menage
2006-10-04 21:40       ` Paul Menage
2006-10-04 21:49         ` Paul Menage

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=20060928114939.d13c957b.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=ckrm-tech@lists.sourceforge.net \
    --cc=dev@sw.ru \
    --cc=jlan@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@google.com \
    --cc=menage@google.com \
    --cc=rohitseth@google.com \
    --cc=sekharan@us.ibm.com \
    --cc=winget@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox