netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Fink <billfink@mindspring.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: Bryan Lawver <lawver1@llnl.gov>,
	Development list <netdev@vger.kernel.org>,
	"Michael S. Tsirkin" <mst@dev.mellanox.co.il>,
	general@lists.openfabrics.org, Linux@lists.openfabrics.org
Subject: Re: [ofa-general] Re: IPoIB forwarding
Date: Sat, 28 Apr 2007 02:51:17 -0400	[thread overview]
Message-ID: <20070428025117.a3b1200a.billfink@mindspring.com> (raw)
In-Reply-To: <4632894D.40705@hp.com>

On Fri, 27 Apr 2007, Rick Jones wrote:

> Bryan Lawver wrote:
> > I had so much debugging turned on that it was not the "slowing of the 
> > traffic" but the "non-coelescencing" that was the remedy.  The NIC is a 
> > MyriCom NIC and these are easy options to set.
> 
> As chance would have it, I've played with some Myricom myri10ge NICs recently, 
> and even disabled large receive offload during some netperf tests :)  It is a 
> modprobe option.  Going back now to the driver source and the README I see :-)
> 
> 
> <excerpt>
> Troubleshooting
> ===============
> 
> Large Receive Offload (LRO) is enabled by default.  This will
> interfere with forwarding TCP traffic.  If you plan to forward TCP
> traffic (using the host with the Myri10GE NIC as a router or bridge),
> you must disable LRO.  To disable LRO, load the myri10ge driver
> with myri10ge_lro set to 0:
> 
>           # modprobe myri10ge myri10ge_lro=0
> 
> Alternatively, you can disable LRO at runtime by disabling
> receive checksum offloading via ethtool:
> 
>     # ethtool -K eth2 rx off
> 
> </excerpt>
> 
> rick jones

What version of the myri10ge driver is this?  With the 1.2.0 version
that comes with the 2.6.20.7 kernel, there is no myri10ge_lro module
parameter.

[root@lang2 ~]# modinfo myri10ge | grep -i lro
[root@lang2 ~]# 

And I've been testing IP forwarding using two Myricom 10-GigE NICs
without setting any special modprobe parameters.

						-Bill

  parent reply	other threads:[~2007-04-28  6:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6.1.2.0.2.20070423160212.12db6400@mail.llnl.gov>
     [not found] ` <20070425124652.GG1624@mellanox.co.il>
     [not found]   ` <6.1.2.0.2.20070426083410.1389d9e0@mail.llnl.gov>
     [not found]     ` <20070426161409.GF15540@mellanox.co.il>
     [not found]       ` <6.1.2.0.2.20070426095112.138e9a68@mail.llnl.gov>
     [not found]         ` <20070426180618.GJ15540@mellanox.co.il>
     [not found]           ` <6.1.2.0.2.20070427115435.13ea5ec0@mail.llnl.gov>
2007-04-27 20:32             ` [ofa-general] Re: IPoIB forwarding Rick Jones
2007-04-27 22:26               ` Bryan Lawver
2007-04-27 22:32                 ` Rick Jones
2007-04-27 22:43                   ` Bryan Lawver
2007-04-27 23:37                     ` Rick Jones
2007-04-27 23:39                       ` David Miller
2007-04-27 23:48                         ` Rick Jones
2007-04-27 23:52                           ` David Miller
2007-04-30 17:16                             ` Rick Jones
2007-05-01 22:43                               ` [PATCH] make myri10ge use default MTU of 1500 bytes Loic Prylli
2007-04-28  6:51                       ` Bill Fink [this message]
2007-04-29 19:40                         ` [ofa-general] Re: IPoIB forwarding Loic Prylli
2007-04-30 21:12                           ` Rick Jones
2007-05-01 22:05                             ` Loic Prylli
2007-05-01 22:12                               ` Rick Jones
2007-05-03 23:37                               ` Bryan Lawver
2007-04-30 17:07                         ` Rick Jones
2007-05-01  5:57                           ` Bill Fink
2007-05-01 16:26                             ` Loic Prylli
2007-04-28  2:35                 ` parks

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=20070428025117.a3b1200a.billfink@mindspring.com \
    --to=billfink@mindspring.com \
    --cc=Linux@lists.openfabrics.org \
    --cc=general@lists.openfabrics.org \
    --cc=lawver1@llnl.gov \
    --cc=mst@dev.mellanox.co.il \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.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).