All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <conman@kolivas.net>
To: Andrew Morton <akpm@digeo.com>
Cc: Marc-Christian Petersen <m.c.p@wolk-project.de>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Andrea Arcangeli <andrea@suse.de>
Subject: Re: [PATCH 2.4.20-aa1] Readlatency-2
Date: Fri, 6 Dec 2002 23:00:42 +1100	[thread overview]
Message-ID: <200212062300.49274.conman@kolivas.net> (raw)
In-Reply-To: <3DF08BC7.62436532@digeo.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>Con Kolivas wrote:
>> io_load:
>> Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
>> 2.4.20 [5]              203.4   33      40      15      3.07
>> 2.4.20aa1 [3]           238.3   27      46      15      3.60
>> 2.4.20aa1rl2 [3]        302.5   22      63      16      4.57
>
>Something must have gone wrong here.  rl2 cannot be worse than
>2.4.20 in this test.
>
>Umm, quick sanity check:
>
>2.4.20-rl2      321.44  147%    96      24%
>2.4.20          361.70  130%    108     24%
>
>So only a 10% speedup, but certainly not a 50% slowdown.  (That is
>on scsi).
>
>Maybe a patch preparation problem?

This seems to be more of a disagreement with -aa1 and -rl2 than -rl2 per se.
Just FYI here's a copy of the SMP results that were in the other thread 
entitled "[PATCH] 2.4.20-rmap15a": 

io_load:
Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
2.4.19 [5]              162.3   45      28      19      4.48
2.4.20 [5]              164.9   45      31      21      4.55
2.4.20-rl2 [3]          101.8   76      19      22      2.81

io_other:
Kernel [runs]           Time    CPU%    Loads   LCPU%   Ratio
2.4.19 [5]              62.3    117     11      20      1.72
2.4.20 [5]              89.6    86      17      21      2.47
2.4.20-rl2 [3]          51.8    142     10      21      1.43

Con
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE98JFqF6dfvkL3i1gRAgKLAJ49oxR+oe3k3UXrUycrsMeFVm8eYACdGmWU
mUuOA1uyw0xhPyQtcxvRyz0=
=OR9G
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2002-12-06 11:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200212061038.27387.m.c.p@wolk-project.de>
2002-12-06  9:45 ` [PATCH 2.4.20-aa1] Readlatency-2 Con Kolivas
2002-12-06 11:36   ` Andrew Morton
2002-12-06 11:41     ` Con Kolivas
2002-12-06 12:00     ` Con Kolivas [this message]
2002-12-05 19:49 Marc-Christian Petersen
2002-12-06  1:24 ` Andrea Arcangeli

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=200212062300.49274.conman@kolivas.net \
    --to=conman@kolivas.net \
    --cc=akpm@digeo.com \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    /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.