From: Chris Friesen <cfriesen@nortelnetworks.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
kernel@nn7.de, linux-kernel@vger.kernel.org,
benh@kernel.crashing.org, netdev@oss.sgi.com, jgarzik@pobox.com
Subject: Re: sungem - ifconfig eth0 mtu 1300 -> oops
Date: Tue, 22 Jun 2004 10:53:23 -0400 [thread overview]
Message-ID: <40D847E3.2080109@nortelnetworks.com> (raw)
In-Reply-To: <20040621141144.119be627.davem@redhat.com>
David S. Miller wrote:
> On Mon, 21 Jun 2004 23:03:16 +1000
> Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> > On Mon, Jun 21, 2004 at 10:33:50PM +1000, Herbert Xu wrote:
> > >
> > > Does this patch fix your problems?
> >
> > Oops, I had a thinko about min vs. max. I've also decided to make the
> > bigger MTU useful by adjusting the arguments to skb_put() as well.
> > Please try this one instead.
>
> Applied, thanks Herbert.
Just a quick question. Does the sungem chip support jumbo frames? I'd like to
use MTU of 9000 to make large local transfers more efficient, but it didn't seem
to work last time I checked.
Thanks,
Chris
next prev parent reply other threads:[~2004-06-22 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1087568322.4455.22.camel@localhost>
2004-06-21 12:33 ` sungem - ifconfig eth0 mtu 1300 -> oops Herbert Xu
2004-06-21 13:03 ` Herbert Xu
2004-06-21 20:24 ` Soeren Sonnenburg
2004-06-21 21:11 ` David S. Miller
2004-06-22 14:53 ` Chris Friesen [this message]
2004-06-22 15:04 ` Jeff Garzik
2004-06-22 16:03 ` Benjamin Herrenschmidt
2004-06-22 19:35 ` David S. Miller
2004-06-21 13:56 ` Manuel Arostegui Ramirez
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=40D847E3.2080109@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jgarzik@pobox.com \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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).