From: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: VM suggestion...
Date: Fri, 8 Jun 2001 01:59:33 +0200 [thread overview]
Message-ID: <20010608015933.F10688@arthur.ubicom.tudelft.nl> (raw)
In-Reply-To: <3B1FEB7E.D06B10A2@mandrakesoft.com> <Pine.LNX.4.21.0106071631150.1156-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0106071631150.1156-100000@freak.distro.conectiva>; from marcelo@conectiva.com.br on Thu, Jun 07, 2001 at 04:36:05PM -0300
On Thu, Jun 07, 2001 at 04:36:05PM -0300, Marcelo Tosatti wrote:
> On Thu, 7 Jun 2001, Jeff Garzik wrote:
> > Statistics like this are cheap to use in runtime and should provide
> > concrete information rather than guesses and estimations...
>
> I've been using LTT (Linux Trace Toolkit) to do similar stuff.
But you can't expect everybody to use LTT. If you just make a couple of
counters and give an easy way to get the values from userspace (proc,
sysctl, syslog), you'll get bug reports with real information. IMHO
data from real world workloads make more sense than "it doesn't work"
reports.
Erik
--
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands
Phone: +31-15-2783635 Fax: +31-15-2781843 Email: J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/
next prev parent reply other threads:[~2001-06-08 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-07 21:00 Jeff Garzik
2001-06-07 19:36 ` Marcelo Tosatti
2001-06-07 22:02 ` Stuart MacDonald
2001-06-07 20:31 ` Marcelo Tosatti
2001-06-07 23:59 ` Erik Mouw [this message]
2001-06-07 22:32 ` Marcelo Tosatti
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=20010608015933.F10688@arthur.ubicom.tudelft.nl \
--to=j.a.k.mouw@its.tudelft.nl \
--cc=jgarzik@mandrakesoft.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
all inboxes | Powered by JetHome®