From: Nick Piggin <piggin@cyberone.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] O1int patch with contest
Date: Sat, 28 Jun 2003 09:11:31 +1000 [thread overview]
Message-ID: <3EFCCF23.4050009@cyberone.com.au> (raw)
In-Reply-To: <200306280041.47619.kernel@kolivas.org>
Con Kolivas wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>I've had some (off list) requests to see if the interactivity patch I posted
>shows any differences in contest. To be honest I wasn't sure it would, and
>this is not quite what I expected. Below is a 2.5.73-mm1 patched with
>patch-O1int-0306271816 (2.5.73-O1i) compared to 2.5.73-mm1 with contest
>(http://contest.kolivas.org).
>
>
Hi Con,
It looks like the patch is starving the background loads.
read_load for example can use up to 7% (maybe more) of the
CPU. It is brought down to 2.2%, list_load is worse.
prev parent reply other threads:[~2003-06-27 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 14:41 [BENCHMARK] O1int patch with contest Con Kolivas
2003-06-27 15:28 ` Felipe Alfaro Solana
2003-06-27 15:40 ` Con Kolivas
2003-06-27 23:38 ` Roberto Orenstein
2003-06-27 23:11 ` Nick Piggin [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=3EFCCF23.4050009@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=kernel@kolivas.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox