From: Stephen Hemminger <shemminger@osdl.org>
To: tim.c.chen@linux.intel.com
Cc: Olaf Kirch <okir@suse.de>, 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, 8 Nov 2006 15:00:07 -0800 [thread overview]
Message-ID: <20061108150007.49eaea68@freekitty> (raw)
In-Reply-To: <1163023652.10806.203.camel@localhost.localdomain>
On Wed, 08 Nov 2006 14:07:32 -0800
Tim Chen <tim.c.chen@linux.intel.com> wrote:
> On Wed, 2006-11-08 at 23:10 +0100, Olaf Kirch wrote:
>
> >
> > In fixing performance issues, the most obvious explanation isn't always
> > the right one. It's quite possible you're right, sure.
> >
> > 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.
> >
>
> I am running Volanomark in a loopback mode on a 2P woodcrest box
> (4 cores). So the configuration is a bit different.
>
> In my testing, the CPU utilization is at 100%. So
> increase in ACKs will cost CPU to devote more
> time to process those ACKs and reduce throughput.
>
> >
> > You could count the number of outbound packets dropped on the server.
> >
>
> As I'm running in loopback mode, there are no dropped packets.
>
Optimizing for loopback is perversion; perversion can be fun but it gets
to be a obsession then it's sick.
--
Stephen Hemminger <shemminger@osdl.org>
next prev parent reply other threads:[~2006-11-08 23:01 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 [this message]
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
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=20061108150007.49eaea68@freekitty \
--to=shemminger@osdl.org \
--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.