From: John Hesterberg <jh@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Jay Lan <jlan@engr.sgi.com>,
linux-kernel@vger.kernel.org, erikj@dbear.engr.sgi.com,
limin@engr.sgi.com, lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: [PATCH] new CSA patchset for 2.6.8
Date: Thu, 26 Aug 2004 13:38:34 -0500 [thread overview]
Message-ID: <20040826183834.GA11393@sgi.com> (raw)
In-Reply-To: <20040825221842.72dd83a4.akpm@osdl.org>
On Wed, Aug 25, 2004 at 10:18:42PM -0700, Andrew Morton wrote:
> Jay Lan <jlan@engr.sgi.com> wrote:
> >
> > I have broken up one big CSA kernel patch into four smaller ones
> > as attached:
> >
> > csa_io - collects io accounting data
> > csa_mm - collects mm accounting data
> > csa_eop - provides a hook to perform end-of-process accounting
> > csa_module - builds csa loadable module
>
> More broadly: Help!
>
> I am 100% not in a position to judge whether Linux needs Comprehensive
> System Accounting, nor am I able to define what the requirements for such a
> thing should be. All I can tell from your patch is the quality of its
> implementation, and that's leaping far, far ahead of where we should be.
Linux needs something beyond what it has today, at least for the
HPC market SGI is familiar with. We believe it will more generally
benefit Linux HPC and enterprise markets, which is one reason we've
released the whole CSA stack as open source.
>
> We're going to need help from you, and from all the other stakeholders in
> judging how useful this feature is to Linux implementors and how well this
> implementation meets the (unknown) requirements. See my problem?
>
> I've cc'ed lse-tech, where enterprise folks hang out. I would request that
> the people who are stakeholders in this feature
>
> a) stick their hands up
We're running CSA in production on Altix (our Itanium/Linux platform)
for several years now.
>
> b) let us know how important this kind of feature is for their users
A substantial number of our customers require it. CSA has been
developed over the years on SGI's HPC systems in response to our
customers needs. It's been reimplemented and opensourced for Linux,
originally as an SGI/LANL collaboration.
> c) review the offered feature set against their requirements
>
> d) let us know how well the implementation fits that requirement and
It fits. :-)
Actually, one secondary feature on our wishlist is 'projects'.
Our customers are tied into the current CSA user interface.
However, there is lots of room for cooperation under that, particularly
in the kernel. We can always consider a migration project as well.
John
next prev parent reply other threads:[~2004-08-26 18:54 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
2004-08-28 1:26 ` Arthur Corliss
[not found] ` <20040827054218.GA4142@frec.bull.fr>
2004-08-27 19:31 ` [Lse-tech] " 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-26 18:38 ` John Hesterberg [this message]
[not found] ` <412EADBC.60607@bigpond.net.au>
[not found] ` <20040826205349.0582d38e.akpm@osdl.org>
2004-08-27 20:24 ` [Lse-tech] " Jay Lan
2004-08-30 19:10 ` John Hesterberg
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=20040826183834.GA11393@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 \
/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