From: Ben Greear <greearb@candelatech.com>
To: danial_thom@yahoo.com
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.12 Performance problems
Date: Wed, 24 Aug 2005 21:51:57 -0700 [thread overview]
Message-ID: <430D4E6D.1090200@candelatech.com> (raw)
In-Reply-To: <20050824172631.11829.qmail@web33309.mail.mud.yahoo.com>
Danial Thom wrote:
> I think the concensus is that 2.6 has made trade
> offs that lower raw throughput, which is what a
> networking device needs. So as a router or
> network appliance, 2.6 seems less suitable. A raw
> bridging test on a 2.0Ghz operton system:
>
> FreeBSD 4.9: Drops no packets at 900K pps
> Linux 2.4.24: Starts dropping packets at 350K pps
> Linux 2.6.12: Starts dropping packets at 100K pps
I ran some quick tests using kernel 2.6.11, 1ms tick (HZ=1000), SMP kernel.
Hardware is P-IV 3.0Ghz + HT on a new SuperMicro motherboard with 64/133Mhz
PCI-X bus. NIC is dual Intel pro/1000. Kernel is close to stock 2.6.11.
I used brctl to create a bridge with the two GigE adapters in it and
used pktgen to stream traffic through it (250kpps in one direction, 1kpps in
the other.)
I see a reasonable amount of drops at 250kpps (60 byte packets):
about 60,000,000 packets received, 20,700 dropped.
Interestingly, the system is about 60% idle according to top,
and still dropping pkts, so it would seem that the system could
be better utilized!
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2005-08-25 4:52 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 16:57 2.6.12 Performance problems Danial Thom
2005-08-23 7:12 ` Helge Hafting
2005-08-23 17:10 ` Danial Thom
2005-08-23 17:21 ` Patrick McHardy
2005-08-24 16:24 ` Danial Thom
2005-08-24 16:35 ` Jesper Juhl
2005-08-24 17:26 ` Danial Thom
2005-08-25 4:51 ` Ben Greear [this message]
2005-08-25 6:08 ` Danial Thom
2005-08-25 6:15 ` Ben Greear
2005-08-26 3:29 ` Danial Thom
2005-08-26 22:18 ` Danial Thom
2005-08-25 6:34 ` Ben Greear
2005-08-25 14:26 ` Danial Thom
2005-08-25 16:55 ` Ben Greear
2005-08-25 20:45 ` Danial Thom
2005-08-26 19:10 ` Benjamin LaHaise
2005-08-27 11:19 ` Vladimir B. Savkin
2005-08-27 14:35 ` Danial Thom
2005-08-23 18:02 ` Sven-Thorsten Dietrich
2005-08-23 20:10 ` Danial Thom
2005-08-23 20:22 ` Sven-Thorsten Dietrich
2005-08-24 16:33 ` Danial Thom
2005-08-23 20:40 ` Patrick McHardy
2005-08-23 23:29 ` Ben Greear
2005-08-24 16:39 ` Danial Thom
2005-08-23 21:32 ` Jesper Juhl
2005-08-24 17:03 ` Danial Thom
[not found] <2230.192.167.206.189.1124721719.squirrel@new.host.name>
2005-08-22 15:41 ` Danial Thom
2005-08-26 13:17 ` Adrian Bunk
2005-08-26 15:34 ` Danial Thom
2005-08-26 16:21 ` Adrian Bunk
2005-08-26 17:06 ` Danial Thom
2005-08-26 18:30 ` Adrian Bunk
2005-08-26 21:09 ` Danial Thom
2005-08-26 23:27 ` Ben Greear
2005-08-27 14:44 ` Danial Thom
[not found] <9a87484905082111205d27c1aa@mail.gmail.com>
2005-08-21 20:21 ` Danial Thom
2005-08-21 21:21 ` Jesper Juhl
2005-08-22 11:46 ` Denis Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2005-08-21 17:07 Danial Thom
2005-08-21 15:46 Danial Thom
2005-08-21 16:15 ` Patrick McHardy
2005-08-21 16:18 ` Danial Thom
2005-08-21 16:36 ` Patrick McHardy
2005-08-21 19:47 ` Andrew Morton
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=430D4E6D.1090200@candelatech.com \
--to=greearb@candelatech.com \
--cc=danial_thom@yahoo.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 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.