From: Rick Jones <rick.jones2@hp.com>
To: Olaf Kirch <okir@suse.de>
Cc: Tim Chen <tim.c.chen@linux.intel.com>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, davem@sunset.davemloft.net,
kuznet@ms2.inr.ac.ru, netdev@vger.kernel.org
Subject: Re: 2.6.19-rc1: Volanomark slowdown
Date: Wed, 08 Nov 2006 17:08:47 -0800 [thread overview]
Message-ID: <1163034527.5931.56.camel@raj-laptop> (raw)
In-Reply-To: <20061108221028.GA16889@suse.de>
On Wed, 2006-11-08 at 23:10 +0100, Olaf Kirch wrote:
> What I'm saying though is that it doesn't rhyme with what I've seen of
> Volanomark - we ran 2.6.16 on a 4p Intel box for instance and it didn't
> come close to saturating a Gigabit pipe before it maxed out on CPU load.
That actually supports the hypothesis doesn't it? The issue being the
increased number of ACKs causing additional CPU overhead not saturating
a NIC if any involved.
One of these days I may have to try to look more closely at what volano
does relative to netperf - I remember that someone tried very hard (was
it you alexy?) to show a perfomance effect with netperf and it didn't do
it :(
rick jones
prev parent reply other threads:[~2006-11-09 1:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 18:32 2.6.19-rc1: Volanomark slowdown Tim Chen
2006-11-07 20:45 ` David Miller
2006-11-07 21:50 ` John Heffner
2006-11-07 22:22 ` David Miller
2006-11-07 22:29 ` John Heffner
2006-11-08 10:07 ` Alexey Kuznetsov
2006-11-08 15:55 ` Arjan van de Ven
2006-11-08 16:29 ` Olaf Kirch
2006-11-08 18:38 ` Tim Chen
2006-11-08 19:44 ` Arjan van de Ven
2006-11-08 22:10 ` Olaf Kirch
2006-11-08 22:07 ` Tim Chen
2006-11-08 23:00 ` Stephen Hemminger
2006-11-08 22:32 ` Tim Chen
2006-11-09 9:21 ` Olaf Kirch
2006-11-08 22:58 ` Stephen Hemminger
2006-11-09 1:08 ` Rick Jones [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=1163034527.5931.56.camel@raj-laptop \
--to=rick.jones2@hp.com \
--cc=arjan@infradead.org \
--cc=davem@sunset.davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=okir@suse.de \
--cc=tim.c.chen@linux.intel.com \
/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.