From: "J.A. Magallon" <jamagallon@able.es>
To: rwhron@earthlink.net
Cc: andrea@suse.de, jamagallon@able.es, linux-kernel@vger.kernel.org,
lse-tech@lists.sourceforge.net
Subject: Re: pipe and af/unix latency differences between aa and jam on smp
Date: Tue, 9 Jul 2002 03:25:34 +0200 [thread overview]
Message-ID: <20020709012534.GE1835@werewolf.able.es> (raw)
In-Reply-To: <20020709005901.GA9616@rushmore>; from rwhron@earthlink.net on Tue, Jul 09, 2002 at 02:59:01 +0200
On 2002.07.09 rwhron@earthlink.net wrote:
>The -jam patchset is interesting because it starts out
>with the entire -aa patchset and adds a few things.
>
>Sometimes small differences in LMbench between -jam and -aa are
>just CPU bounces on SMP. The difference for pipe and af/unix latency
>only appears on SMP too, but it is very consistent. (My k6/2
>has small differences between -aa and -jam for pipe and af/unix
>latency).
>
>You will know better what could make the difference:
>
>This is the averages:
>
>*Local* Communication latencies in microseconds - smaller is better
>-------------------------------------------------------------------
>kernel Pipe AF/Unix
>----------------- ------- -------
>2.4.19-pre10-aa4 33.941 70.216
>2.4.19-pre10-jam2 7.877 16.699
>
I took a look at your numbers:
*Local* Communication latencies in microseconds - smaller is better
-------------------------------------------------------------------
kernel Pipe AF/Unix UDP RPC/UDP TCP RPC/TCP TCPconn
----------------------------- ------- ------- ------- ------- ------- ------- -------
2.4.19-pre7-jam6 29.513 42.369 58.6165 60.7792 50.2572 82.4976 87.321
2.4.19-pre8-jam2 7.697 15.274 59.6730 60.8190 55.276 82.1297 89.416
2.4.19-pre8-jam2-nowuos 7.739 14.929 57.9326 60.5497 55.9745 81.8908 90.370
(last line says that wake-up-sync is not responsible...)
Main changes between first two were irqbalance and ide6->ide10.
--
J.A. Magallon \ Software is like sex: It's better when it's free
mailto:jamagallon@able.es \ -- Linus Torvalds, FSF T-shirt
Linux werewolf 2.4.19-rc1-jam2, Mandrake Linux 8.3 (Cooker) for i586
gcc (GCC) 3.1.1 (Mandrake Linux 8.3 3.1.1-0.7mdk)
next prev parent reply other threads:[~2002-07-09 1:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 0:59 pipe and af/unix latency differences between aa and jam on smp rwhron
2002-07-09 1:11 ` J.A. Magallon
2002-07-09 1:15 ` J.A. Magallon
2002-07-09 10:19 ` Zwane Mwaikambo
2002-07-09 1:25 ` J.A. Magallon [this message]
2002-07-11 20:20 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 14:05 rwhron
2002-07-09 14:53 ` Andrea Arcangeli
2002-07-11 9:02 rwhron
2002-07-11 9:21 ` Andrea Arcangeli
2002-07-12 1:27 rwhron
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=20020709012534.GE1835@werewolf.able.es \
--to=jamagallon@able.es \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=rwhron@earthlink.net \
/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