From: Christoph Hellwig <hch@infradead.org>
To: Rik van Riel <riel@redhat.com>
Cc: 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 17:45:43 +0100 [thread overview]
Message-ID: <20040430174543.A13431@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0404301122200.6976-100000@chimarrao.boston.redhat.com>; from riel@redhat.com on Fri, Apr 30, 2004 at 11:22:49AM -0400
On Fri, Apr 30, 2004 at 11:22:49AM -0400, Rik van Riel wrote:
> > Again, pagg doesn't even play in that league. It's really just a tiny
> > meachnism to allow a kernel module keep per-process data. Policies like
> > process-groups can be implemented on top of that.
>
> So basically you're arguing that PAGG is better because it
> doesn't do what's needed ? ;)
I told you a bunch of times that's it's a different thing. Simply keeping
per-process state might be a useful building block for some monster resource
whatever fuckup, but certainly not the other way around.
next prev parent reply other threads:[~2004-04-30 16:45 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 [this message]
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=20040430174543.A13431@infradead.org \
--to=hch@infradead.org \
--cc=chrisw@osdl.org \
--cc=erikj@subway.americas.sgi.com \
--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.