netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ray Lehtiniemi <rayl@mail.com>
To: Scott Feldman <sfeldma@pobox.com>
Cc: netdev@oss.sgi.com
Subject: Re: how to tune a pair of e1000 cards on intel e7501-based system?
Date: Sun, 5 Dec 2004 21:10:03 -0700	[thread overview]
Message-ID: <20041206041002.GC7891@mail.com> (raw)
In-Reply-To: <1102304058.3343.217.camel@sfeldma-mobl.dsl-verizon.net>

On Sun, Dec 05, 2004 at 07:34:18PM -0800, Scott Feldman wrote:
> On Sun, 2004-12-05 at 18:44, Ray Lehtiniemi wrote:
> > i'm trying to understand how to tune a pair of e1000 cards in
> > a server box.  the box is a dual xeon 3.06 with hyperthreading,
> > using the intel e7501 chipset, with both cards on hub interface
> > D.  the application involves small UDP packets, generally under
> 
> These are 82544 cards hanging of P64H2, so they're running at PCI-X, but
> at what speed?  Run ethtool -d eth<x> | grep Bus.

:-)  just found ethtool and compiled it before i read this email.  any other
useful tools i should get?



> The cards support
> 133Mhz, but having them adjacent on the same P64H2 probably bumps them
> down to 100Mhz.

# ethtool -d eth0 | grep Bus
      Bus type:                          PCI-X
      Bus speed:                         133MHz
      Bus width:                         64-bit
# ethtool -d eth1 | grep Bus
      Bus type:                          PCI-X
      Bus speed:                         133MHz
      Bus width:                         64-bit

so that looks okay...

any idea why lspci -vv shows non-64bit, non-133 MHz?  (i am assuming
that is what the minus sign means)

        Capabilities: [e4] PCI-X non-bridge device.
                Command: DPERE- ERO+ RBC=0 OST=0
                Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-



> Can you put one on D and the other on another bus?

not sure... have to look at the chassis tomorrow morning. a co-worker
actually built the box, i've not seen it in person yet.




> There is a lot of current traffic on netdev about this topic.  netdev is
> the official e1000 mailing this weekend.  :-)

i noticed that almost half of the messages in the e1000-devel archives
since oct 2002 were sent in the last 10 days :-)


> What kind of numbers are you getting?

will start testing tomorrow, just starting my background research tonight


> What kernel are you using?

2.4.20 with driver 4.4.12-k1, and 2.6.bkcurr with driver 5.bkcurr



> What driver tweaks have you made, if any?

none yet.  based on mailing list searches, i plan to:

 - InterruptThrottleRate 15000
 - TxIntDelay 0

i also plan to set rp_filter to zero for all interfaces.



thanks

-- 
----------------------------------------------------------------------
     Ray L   <rayl@mail.com>

  reply	other threads:[~2004-12-06  4:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06  2:44 how to tune a pair of e1000 cards on intel e7501-based system? Ray Lehtiniemi
2004-12-06  3:34 ` Scott Feldman
2004-12-06  4:10   ` Ray Lehtiniemi [this message]
2004-12-06 23:12     ` Ray Lehtiniemi
  -- strict thread matches above, loose matches on Subject: below --
2004-12-08  1:10 Brandeburg, Jesse

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=20041206041002.GC7891@mail.com \
    --to=rayl@mail.com \
    --cc=netdev@oss.sgi.com \
    --cc=sfeldma@pobox.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;
as well as URLs for NNTP newsgroup(s).