public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Cc: "Feldman, Scott" <scott.feldman@intel.com>
Subject: e1000 performance
Date: Tue, 29 Jul 2003 00:28:53 +0200	[thread overview]
Message-ID: <20030728222853.GA2446@werewolf.able.es> (raw)

Hi.

I think I am getting weird performace with e1000 in 2.4.22-pre.
NetPipe gives this numbers for e1000:

Node receiver...
Master transmitter...
Latency: 0.000040
Now starting main loop
  0:      4096 bytes    7 times -->  264.18 Mbps in 0.000118 sec
  1:      8192 bytes    7 times -->  397.55 Mbps in 0.000157 sec
  2:     12288 bytes  795 times -->  475.30 Mbps in 0.000197 sec
  3:     16384 bytes  845 times -->  524.12 Mbps in 0.000238 sec
  4:     20480 bytes  786 times -->  566.84 Mbps in 0.000276 sec
  5:     24576 bytes  725 times -->  586.49 Mbps in 0.000320 sec
  6:     28672 bytes  651 times -->  605.81 Mbps in 0.000361 sec
  7:     32768 bytes  593 times -->  618.25 Mbps in 0.000404 sec
  8:     36864 bytes  540 times -->  579.82 Mbps in 0.000485 sec
  9:     40960 bytes  458 times -->  579.72 Mbps in 0.000539 sec
 10:     45056 bytes  417 times -->  565.82 Mbps in 0.000608 sec
 11:     49152 bytes  374 times -->  569.07 Mbps in 0.000659 sec
 12:     53248 bytes  347 times -->  576.62 Mbps in 0.000705 sec
 13:     57344 bytes  327 times -->  584.06 Mbps in 0.000749 sec
 14:     61440 bytes  309 times -->  587.31 Mbps in 0.000798 sec
 15:     65536 bytes  292 times -->  592.25 Mbps in 0.000844 sec
 16:     69632 bytes  277 times -->  577.42 Mbps in 0.000920 sec
 17:     73728 bytes  255 times -->  566.39 Mbps in 0.000993 sec
 18:     77824 bytes  237 times --> 

Hardware:
03:01.0 Ethernet controller: Intel Corp. 82543GC Gigabit Ethernet Controller (Copper) (rev 02)

Kernel is 2.4.22-pre8, patch for MMX/SSE checksums applied:
Measuring network checksumming speed
   basic     :   768.000 MB/sec
   simple    :   665.600 MB/sec
func 3Dnow! skipped: not supported by CPU
func AMD-MMX skipped: not supported by CPU
   SSE1+     :   819.200 MB/sec
csum: using csum function: SSE1+
   basic     :   537.600 MB/sec
   simple    :   537.600 MB/sec
func AMD-MMX skipped: not supported by CPU
   SSE1+     :   588.800 MB/sec
   SSE1      :   691.200 MB/sec
csum: using csum_copy function: SSE1

No modules parameters for e1000 (default behaviour), no mtu changes, nothing.

Any ideas to up performance ?

TIA

-- 
J.A. Magallon <jamagallon@able.es>      \                 Software is like sex:
werewolf.able.es                         \           It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.22-pre8-jam1m (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-0.6mdk))

             reply	other threads:[~2003-07-28 22:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 22:28 J.A. Magallon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-30  6:52 e1000 performance Feldman, Scott
2003-07-30 22:28 ` J.A. Magallon
2003-07-30 22:55 Feldman, Scott

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=20030728222853.GA2446@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott.feldman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox