From: Jesper Krogh <jesper@krogh.cc>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Status update on Sun Neptune 10Gbit fibre using the NIU-driver.
Date: Sun, 22 Mar 2009 10:11:42 +0100 [thread overview]
Message-ID: <49C600CE.70704@krogh.cc> (raw)
Hi.
Back in the 2.6.25/26-days .. (around 9 months ago) I had som stuggles
getting both performance and stabillity out of a Sun Neptune 10Gbit NIC
over fibre. The NIU driver blew up on the system under load but Matheos
Worku send me an internal Sun driver (nxge) that performed fairly well.
It peaked out around 800-850 MB/s .. it put a fairly high load on the
host system and peaked with over 300.000 cs/s (both numbers measured
with dstat).
Today I got around to tesing the NIU(2.6.27.20) driver again. Having
repeated the test I did last summer I couldn't get it to "blow up". But
instead of the ~500MB/s i got out of it last summer, it peaks at 940MB/s
now and the load on the host is nearly invisible (<2) .. cs rates less
than 10K mostly.
I'm not using any kind of Jumbo frames in the setup.
I'll keep it up on the niu-driver for now and report back if it
encounters any problems.
In the test .. I do dd over NFS, default exports, default mount options
.. dd have "bs" set to either 1M or to 512 (to try to stress the NFS
server). I have tried to put cpu-load in the NFS-server while running
the NFS-server and pushing some data around on them memory subsystem
while doing it.
This is just excellent.. (crossing fingers that it can beat the 180
days of uptime the nxge-driver got).
Link to old struggles:
http://thread.gmane.org/gmane.linux.kernel/677545
Jesper
--
Jesper
next reply other threads:[~2009-03-22 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 9:11 Jesper Krogh [this message]
2009-03-22 15:36 ` Status update on Sun Neptune 10Gbit fibre using the NIU-driver Eric Dumazet
2009-03-22 16:39 ` Jesper Krogh
2009-03-22 18:01 ` Jesper Krogh
2009-03-22 18:17 ` Jesper Krogh
2009-03-22 19:18 ` Eric Dumazet
2009-03-22 19:17 ` Eric Dumazet
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=49C600CE.70704@krogh.cc \
--to=jesper@krogh.cc \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).