From: Chris Wright <chrisw@osdl.org>
To: Shailabh <nagar@watson.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Rik van Riel <riel@redhat.com>,
Erik Jacobson <erikj@subway.americas.sgi.com>,
Paul Jackson <pj@sgi.com>,
chrisw@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Process Aggregates (PAGG) support for the 2.6 kernel
Date: Fri, 30 Apr 2004 11:15:43 -0700 [thread overview]
Message-ID: <20040430111543.X21045@build.pdx.osdl.net> (raw)
In-Reply-To: <40929297.2030903@watson.ibm.com>; from nagar@watson.ibm.com on Fri, Apr 30, 2004 at 01:53:27PM -0400
* Shailabh (nagar@watson.ibm.com) wrote:
> In CKRM, the premise is that the privileged user defines the way
> processes get grouped and could do so in a way that leads to rapid
> changes in group membership. So having group control/monitoring
> policies implemented as an externally loaded module (not talking of
> scheduler modifications as modules, which is a no-no) is not a
> palatable option.
Yes, this is why I looked at the PAGG job module. I was looking for how
it might have mucked (externally) with scheduler. At any rate, I found
all the primitives for joining/leaving/defining groups here which I'd
have expected closer to core.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-04-30 18:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 22:04 [PATCH] Process Aggregates (PAGG) support for the 2.6 kernel Erik Jacobson
2004-04-26 23:39 ` Chris Wright
2004-04-27 0:36 ` Jesse Barnes
2004-04-27 0:41 ` Chris Wright
2004-04-27 21:00 ` Erik Jacobson
2004-04-27 21:05 ` Chris Wright
2004-04-29 21:10 ` Rik van Riel
2004-04-27 20:51 ` Erik Jacobson
2004-04-27 22:28 ` Chris Wright
2004-04-28 14:55 ` Christoph Hellwig
2004-04-29 19:20 ` Paul Jackson
2004-04-29 19:27 ` Chris Wright
2004-04-29 19:29 ` Christoph Hellwig
2004-04-29 19:34 ` Paul Jackson
2004-04-29 19:53 ` Erik Jacobson
2004-04-29 21:20 ` Rik van Riel
2004-04-30 6:17 ` Christoph Hellwig
2004-04-30 11:08 ` Guillaume Thouvenin
2004-04-30 18:00 ` Shailabh
2004-04-30 18:28 ` Rik van Riel
2004-04-30 12:54 ` Rik van Riel
2004-04-30 13:06 ` Christoph Hellwig
2004-04-30 13:28 ` Chris Mason
2004-04-30 16:50 ` Shailabh
2004-04-30 15:22 ` Rik van Riel
2004-04-30 16:45 ` Christoph Hellwig
2004-04-30 17:53 ` Shailabh
2004-04-30 18:15 ` Chris Wright [this message]
2004-04-30 15:59 ` Chris Wright
2004-04-30 8:54 ` Guillaume Thouvenin
2004-05-20 21:16 ` Erik Jacobson
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=20040430111543.X21045@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=erikj@subway.americas.sgi.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nagar@watson.ibm.com \
--cc=pj@sgi.com \
--cc=riel@redhat.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.