From: Robert Love <rml@tech9.net>
To: J Sloan <jjs@pobox.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Encouraging results from 2.4.10-pre14 + preempt
Date: 22 Sep 2001 23:06:26 -0400 [thread overview]
Message-ID: <1001214391.872.36.camel@phantasy> (raw)
In-Reply-To: <3BAD2F22.6E151CBD@pobox.com>
In-Reply-To: <3BAD2F22.6E151CBD@pobox.com>
On Sat, 2001-09-22 at 20:38, J Sloan wrote:
> I am very encouraged by the latest linus kernel, and
> thought I'd pass this along -
I appreciate this.
> Highlights -
> ------------
> - There was absolutely no mp3 skipping during dbench 16 & 32.
> - There was minor skipping during dbench 40, when load was near 40.
> - Best of all, the desktop remained completely responsive the entire
> time.
This is great. While I am sure all three of this points wouldn't be
true without preempt patch, I would be interested in seeing your opinion
of the comparison between with and without, if you had the time. Also
comparing the dbench would be nice, but you must be careful to replicate
the system similarly.
Thanks much for the feedback,
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
prev parent reply other threads:[~2001-09-23 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-23 0:38 Encouraging results from 2.4.10-pre14 + preempt J Sloan
2001-09-23 3:06 ` Robert Love [this message]
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=1001214391.872.36.camel@phantasy \
--to=rml@tech9.net \
--cc=jjs@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.