From: Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca>
To: Christoph Hellwig <hch@infradead.org>
Cc: 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 13:08:20 +0200 [thread overview]
Message-ID: <1083323300.409233a4459e3@www.imp.polymtl.ca> (raw)
In-Reply-To: <20040430071750.A8515@infradead.org>
Selon Christoph Hellwig <hch@infradead.org>:
> > I suspect there's a rather good chance of merging a common
> > PAGG/CKRM infrastructure, since they pretty much do the same
> > thing at the core and they both have different functionality
> > implemented on top of the core process grouping.
>
> Still doesn't make a lot of sense. CKRM is a huge cludgy beast poking
> everywhere while PAGG is a really small layer to allow kernel modules
> keeping per-process state. If CKRM gets merged at all (and the current
> looks far to horrible and the gains are rather unclear) it should layer
> ontop of something like PAGG for the functionality covered by it.
And what about put the management of containers outside the kernel. We could for
exemple use a program that will listen file /proc/acct_event and execute a
programs to handle the event like ACPID does. Of course it will need some kernel
modifications but those modifications will be small as process aggregation will
be done outside the kernel. We could also use relayfs to exchange datas between
user program and the kernel.
Guillaume
next prev parent reply other threads:[~2004-04-30 11:09 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 [this message]
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
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=1083323300.409233a4459e3@www.imp.polymtl.ca \
--to=guillaume.thouvenin@polymtl.ca \
--cc=chrisw@osdl.org \
--cc=erikj@subway.americas.sgi.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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.