netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Krogh <jesper@krogh.cc>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Status update on Sun Neptune 10Gbit fibre using the NIU-driver.
Date: Sun, 22 Mar 2009 17:39:36 +0100	[thread overview]
Message-ID: <49C669C8.70902@krogh.cc> (raw)
In-Reply-To: <49C65AFC.3080300@cosmosbay.com>

Eric Dumazet wrote:
> Jesper Krogh a écrit :
>> 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
> 
> Yes I remember this stuff. David added multi tx queue support in last July
> (for 2.6.27)

Can there be something about "fairness" changed? While producing the 
screenshot to you below I got this one on the server:
do_ypcall: clnt_call: RPC: Unable to send; errno = No buffer space available

So NIS wasn't able to get throgh..

> Could you post more information please, about load on individual cpus
>  for example ? (top snapshot with one line per cpu)

http://krogh.cc/~jesper/top.png

> Is NFS using TCP or UDP on your setup ?

TCP.

> An interesting test would be the reverse path (transmit from clients to
> this server)

Thats harder to setup and not be "disk IO-bound on the server". Perhaps 
exporting a RAM-disk and write into that?

> Also, testing 2.6.29 could be interesting, since UDP receive
> path doesnt need to use a global rwlock anymore.

I'll put that on my todo list..

-- 
Jesper

  reply	other threads:[~2009-03-22 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-22  9:11 Status update on Sun Neptune 10Gbit fibre using the NIU-driver Jesper Krogh
2009-03-22 15:36 ` Eric Dumazet
2009-03-22 16:39   ` Jesper Krogh [this message]
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=49C669C8.70902@krogh.cc \
    --to=jesper@krogh.cc \
    --cc=dada1@cosmosbay.com \
    --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).