From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: John Stoffel <stoffel@casc.com>
Cc: Mike Galbraith <mikeg@wen-online.de>,
Tobias Ringstrom <tori@unhappy.mine.nu>,
Jonathan Morton <chromi@cyberspace.org>,
Shane Nay <shane@minirl.com>,
"Dr S.M. Huen" <smh1008@cus.cam.ac.uk>,
Sean Hunter <sean@dev.sportingbet.com>,
Xavier Bestel <xavier.bestel@free.fr>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: VM Report was:Re: Break 2.4 VM in five easy steps
Date: Fri, 8 Jun 2001 17:04:33 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.21.0106081701300.2422-100000@freak.distro.conectiva> (raw)
In-Reply-To: <15137.15472.264539.290588@gargle.gargle.HOWL>
On Fri, 8 Jun 2001, John Stoffel wrote:
>
> Marcelo> Now the stock kernel gives us crappy interactivity compared
> Marcelo> to my patch. (Note: my patch still does not gives me the
> Marcelo> interactivity I want under high VM loads, but I hope to get
> Marcelo> there soon).
>
> This raises the important question, how can we objectively measure
> interactive response in the kernel and relate it to the user's
> perceived interactive response? If we could come up with some sort of
> testing system that would show us this, it would help alot, since we
> could just have people run tests in a more automatic and repeatable
> manner.
>
> And I think it would also help us automatically tune the Kernel, since
> it would have a knowledge of it's own performance.
>
> There is the problem in terms of some people want pure interactive
> performance, while others are looking for throughput over all else,
> but those are both extremes of the spectrum. Though I suspect
> raw throughput is the less wanted (in terms of numbers of systems)
> than keeping interactive response good during VM pressure.
And this raises a very very important point: raw throughtput wins
enterprise-like benchmarks, and the enterprise people are the ones who pay
most of hackers here. (including me and Rik)
We have to be careful about that.
> I have zero knowledge of how we could do this, but giving the kernel
> some counters, even if only for use during debugging runs, which would
> give us some objective feedback on performance would be a big win.
>
> Having people just send in reports of "I ran X,Y,Z and it was slow"
> doesn't help us, since it's so hard to re-create their environment so
> you can run tests against it.
Lets wait for some test system to be set up (eg the OSDL thing).
Once thats done, I'm sure we will find out some way of doing it.
Well, good weekend for you too.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-06-08 20:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0106071722450.1156-100000@freak.distro.conectiva>
2001-06-07 23:29 ` Shane Nay
2001-06-08 1:18 ` Jonathan Morton
2001-06-08 12:50 ` Mike Galbraith
2001-06-08 14:19 ` Tobias Ringstrom
2001-06-08 15:51 ` John Stoffel
2001-06-08 17:01 ` Mike Galbraith
2001-06-08 17:43 ` John Stoffel
2001-06-08 17:35 ` Marcelo Tosatti
2001-06-08 20:58 ` John Stoffel
2001-06-08 20:04 ` Marcelo Tosatti [this message]
2001-06-08 23:44 ` Jonathan Morton
2001-06-09 2:36 ` Andrew Morton
2001-06-09 3:43 ` Mike Galbraith
2001-06-09 4:05 ` Jonathan Morton
2001-06-09 5:09 ` Mike Galbraith
2001-06-09 5:07 ` Mike Galbraith
2001-06-08 18:30 ` Mike Galbraith
2001-06-09 12:31 ` Zlatko Calusic
2001-06-09 3:34 ` Rik van Riel
2001-06-08 16:51 ` Mike Galbraith
2001-06-08 19:09 ` Tobias Ringstrom
2001-06-09 4:36 ` Mike Galbraith
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=Pine.LNX.4.21.0106081701300.2422-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=chromi@cyberspace.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mikeg@wen-online.de \
--cc=sean@dev.sportingbet.com \
--cc=shane@minirl.com \
--cc=smh1008@cus.cam.ac.uk \
--cc=stoffel@casc.com \
--cc=tori@unhappy.mine.nu \
--cc=xavier.bestel@free.fr \
/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