From: Cliff White <cliffw@osdl.org>
To: scott_list@mischko.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Plans for better performance metrics in upcoming kernels?
Date: Mon, 08 Sep 2003 15:51:27 -0700 [thread overview]
Message-ID: <200309082251.h88MpRX30963@mail.osdl.org> (raw)
In-Reply-To: Message from Craig Thomas <craiger@osdl.org> of "08 Sep 2003 15:27:14 PDT." <1063060034.16303.23.camel@bullpen.pdx.osdl.net>
> We have a project to maintain and improve systat here at OSDL. We're
> looking for others to help in this area, if your're interested.
>
> On Mon, 2003-09-08 at 07:54, Scott Chapman wrote:
> > Hi all,
> >
> > I received one reply to this email. I take it there is nobody really heading
> > up the implementation of improved/missing performance metrics in the kernel?
> >
> > Is this on anyone's radar?
> >
> > What is Linus' take on more/better metrics?
> > Is he likely to roll them in if they are implemented?
> >
> > Is there any plan to implement any existing patches?
> >
> > If I can get developer time applied to this project, I don't want to re-invent
> > the existing pieces. Who do I coordinate with?
OSDL can also provide you hardware resources, if you want to do a project.
We may be able to help some with the coordination, if bandwidth allows.
OSDL is definately interested in improving performance metrics.
cliffw
> >
> > Cordially,
> > Scott
> >
> > On Friday 05 September 2003 16:41, Scott Chapman wrote:
> > > Hi,
> > > I'm wondering what the plans are for more accurate and more useful
> > > performance metrics in upcoming kernels.
> > >
> > > CPU Utilization by process is apparently a known-inaccuracy.
> > >
> > > There are no disk I/O metrics per process.
> > >
> > > CPU Queue Length doesn't appear to be available?
> > >
> > > Etc.
> > >
> > > Linux clearly falls behind the competition in this area. It makes it rather
> > > tough to do system performance analysis on a Linux box! :-)
> > >
> > > Is there a plan to deal with these issues? ETA's?
> > >
> > > Cordially,
> > > Scott
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> --
> Craig Thomas
> craiger@osdl.org
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-09-08 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 23:41 Scott Chapman
2003-09-06 7:28 ` Nick Piggin
2003-09-08 14:54 ` Scott Chapman
2003-09-08 22:27 ` Craig Thomas
2003-09-08 22:51 ` Cliff White [this message]
2003-09-08 23:15 ` Peter Chubb
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=200309082251.h88MpRX30963@mail.osdl.org \
--to=cliffw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott_list@mischko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®