linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ashutosh Naik <ashutosh.naik@gmail.com>
To: Ben Greear <greearb@candelatech.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-net@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	jgarzik@pobox.com
Subject: Re: [RFC] Poor Network Performance with e1000 on 2.6.14.3
Date: Wed, 1 Feb 2006 17:49:18 +0530	[thread overview]
Message-ID: <81083a450602010419l16e6c2f2ldf1f87bff2582662@mail.gmail.com> (raw)
In-Reply-To: <43E04712.6080108@candelatech.com>

[-- Attachment #1: Type: text/plain, Size: 821 bytes --]

On 2/1/06, Ben Greear <greearb@candelatech.com> wrote:
> Ashutosh Naik wrote:
> > Now, I assume that on Gigabit ethernet, I should be getting Line Rate,
> > which is around 220 MBps. Even the CPU is not getting max-ed out here
> > and I am at a loss to understand this behaviour.
>
> Make sure you are running 64-bit 100+Mhz PCI, otherwise you will not
> get line speed.  ethtool -d [device]
> may get that info for you.

Thanks for that Ben. I now used a 64 bit,133 MHz PCI-X on both
machines and I got around  180 MBps, (86259.48 + 95164.90 ), which is
still a decent way away from Line speed. I think PCI is not a
bottleneck now, although I could be wrong. What could I be missing,
and has anybody seen line speed ( 220 MBps ) with e1000 ?

Regards and Thanks
Ashutosh

ps - Attaching my ettcp log

[-- Attachment #2: log.txt --]
[-- Type: text/plain, Size: 1224 bytes --]

[root@localhost ~]# ettcp -s -t -i 300ttcp-r: accept from 192.168.90.100
User: 17553  Nice: 0  System 8885  Idle:737051  Params:4

ttcp-t: buflen=65536, nbuf=2048, align=16384/0, port=5001  tcp  -> 192.168.90.10
0
nttcp-t: socket
nttcp-t: connect
User: 17555  Nice: 0  System 8892  Idle:737076  Params:4
^[
User: 19818  Nice: 0  System 14716  Idle:747604  Params:4
User_diff: 2265  Nice_diff: 0  System_diff: 5831  Idle_diff:10553 Tot:18649
User: 12.145423  System: 31.267092  Nice 0.000000  Idle:56.587485        
nttcp-r: Buflen:65536 SysLoad:31.27% 29232070656 bytes 299.97secs =95164.90 KB/s
ec
nttcp-r: 699884 I/O calls, msec/call = 0.44, calls/sec = 2333.15
nttcp-r: 0.2user 32.6sys 4:59real 10% 0i+0d 0maxrss 0+30pf 691228+3947csw
User: 19834  Nice: 0  System 14722  Idle:747623  Params:4
User_diff: 2279  Nice_diff: 0  System_diff: 5830  Idle_diff:10547 Tot:18656
User: 12.215909  System: 31.250000  Nice 0.000000  Idle:56.534091        
nttcp-t: Buflen:65536 SysLoad:31.25% 26499153920 bytes 300.00secs =86259.48 KB/s
ec
nttcp-t: 404345 I/O calls, msec/call = 0.76, calls/sec = 1347.80
nttcp-t: 0.2user 44.9sys 5:00real 15% 0i+0d 0maxrss 0+30pf 374765+1306csw
[1]+  Done                    ettcp -s -r -l 65536





      parent reply	other threads:[~2006-02-01 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01  5:17 [RFC] Poor Network Performance with e1000 on 2.6.14.3 Ashutosh Naik
     [not found] ` <43E04712.6080108@candelatech.com>
2006-02-01 12:19   ` Ashutosh Naik [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=81083a450602010419l16e6c2f2ldf1f87bff2582662@mail.gmail.com \
    --to=ashutosh.naik@gmail.com \
    --cc=akpm@osdl.org \
    --cc=greearb@candelatech.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@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 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).