From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "Marcelo Tosatti" <marcelo@conectiva.com.br>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: VM suggestion...
Date: Thu, 7 Jun 2001 18:02:51 -0400 [thread overview]
Message-ID: <0dc301c0ef9d$98d0d260$294b82ce@connecttech.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0106071631150.1156-100000@freak.distro.conectiva>
From: "Marcelo Tosatti" <marcelo@conectiva.com.br>
> The problem is that we _cannot_ base ourselves simply on practical results
> from a _limited_ amount of workloads. Also remember the tests we (at least
> I do) are benchmarks which try to use all resources all the time upon
> completion.
Isn't this the point of the X.odd.Y kernels? Spit the stats out into the
syslog, along with a message of "If you see these, please mail them
along to marcelo@conectiva.com.br and a description of your workload
if it's not too much trouble."
..Stu
next prev parent reply other threads:[~2001-06-07 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-07 21:00 VM suggestion Jeff Garzik
2001-06-07 19:36 ` Marcelo Tosatti
2001-06-07 22:02 ` Stuart MacDonald [this message]
2001-06-07 20:31 ` Marcelo Tosatti
2001-06-07 23:59 ` Erik Mouw
2001-06-07 22:32 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2001-06-08 10:46 Martin.Knoblauch
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='0dc301c0ef9d$98d0d260$294b82ce@connecttech.com' \
--to=stuartm@connecttech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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