From: John Hesterberg <jh@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Peter Williams <pwil3058@bigpond.net.au>,
jlan@engr.sgi.com, linux-kernel@vger.kernel.org,
erikj@dbear.engr.sgi.com, limin@engr.sgi.com,
lse-tech@lists.sourceforge.net,
Tim Schmielau <tim@physik3.uni-rostock.de>
Subject: Re: [Lse-tech] Re: [PATCH] new CSA patchset for 2.6.8
Date: Mon, 30 Aug 2004 14:10:32 -0500 [thread overview]
Message-ID: <20040830191032.GA5255@sgi.com> (raw)
In-Reply-To: <20040826205349.0582d38e.akpm@osdl.org>
On Thu, Aug 26, 2004 at 08:53:49PM -0700, Andrew Morton wrote:
> Thanks, guys. So we now know that there are three potential
> implementations which do much the same thing, yes?
I believe CSA does than the others.
> I didn't get a sense of a preferred direction, but at least nobody is
> flaming anybody else yet ;)
>
> It strikes me that CSA is the most actively developed and is the furthest
> along. But that enhancing BSD accounting might be the least intrusive and
> most back-compatible approach.
>
> Is that a fair summary? If not, what should I have said?
Does anyone know if CSA is a super-set of BSD accounting and ELSA?
What would be missing?
I'm unconvinced that enhancing BSD accounting to encompass the
capabilities of CSA is appropriate.
I think we can make the data collection additions common. That should
encompass the bulk of the invasive changes that are required by at least
CSA proper (ie there are still the PAGG changes for job support that we
can discuss separately). Not sure about BSD accounting and ELSA.
With that cooperation, we can then either proceed with further
cooperation, or if the goals and users of the different accounting
approaches dictate different kernel modules and user support,
I'd propose that might be OK.
John
prev parent reply other threads:[~2004-08-30 19:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 0:25 [PATCH] new CSA patchset for 2.6.8 Jay Lan
2004-08-26 5:18 ` Andrew Morton
2004-08-26 17:15 ` Tim Schmielau
2004-08-26 18:26 ` [Lse-tech] " Jay Lan
2004-08-26 19:44 ` Arthur Corliss
2004-08-26 18:43 ` John Hesterberg
2004-08-27 8:26 ` Tim Schmielau
2004-08-26 19:24 ` Arthur Corliss
2004-08-26 20:05 ` Tim Schmielau
2004-08-26 20:46 ` Jay Lan
2004-08-28 1:27 ` Arthur Corliss
2004-08-30 12:26 ` Guillaume Thouvenin
2004-08-31 14:19 ` Tim Schmielau
2004-08-31 23:01 ` [Lse-tech] " Jay Lan
2004-09-08 18:32 ` Jay Lan
[not found] ` <20040827054218.GA4142@frec.bull.fr>
2004-08-27 19:31 ` John Hesterberg
2004-08-30 8:29 ` Tim Schmielau
2004-08-27 19:55 ` Jay Lan
2004-08-31 9:06 ` Guillaume Thouvenin
2004-08-31 10:29 ` Guillaume Thouvenin
2004-08-31 16:04 ` Limin Gu
2004-09-01 21:44 ` John Hesterberg
2004-08-28 1:33 ` Arthur Corliss
2004-08-28 1:26 ` Arthur Corliss
2004-08-26 18:38 ` [Lse-tech] " John Hesterberg
[not found] ` <412EADBC.60607@bigpond.net.au>
[not found] ` <20040826205349.0582d38e.akpm@osdl.org>
2004-08-27 20:24 ` Jay Lan
2004-08-30 19:10 ` John Hesterberg [this message]
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=20040830191032.GA5255@sgi.com \
--to=jh@sgi.com \
--cc=akpm@osdl.org \
--cc=erikj@dbear.engr.sgi.com \
--cc=jlan@engr.sgi.com \
--cc=limin@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=pwil3058@bigpond.net.au \
--cc=tim@physik3.uni-rostock.de \
/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