netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: P@draigBrady.com
To: e1000-devel@lists.sourceforge.net
Cc: netdev@oss.sgi.com
Subject: Re: [E1000-devel] e1000 jumbo problems
Date: Wed, 23 Jun 2004 18:35:39 +0100	[thread overview]
Message-ID: <40D9BF6B.4050807@draigBrady.com> (raw)
In-Reply-To: <40D883C2.7010106@draigBrady.com>

P@draigBrady.com wrote:
> Another related issue, is that the driver uses 4KiB buffers
> for MTUs in the 1500 -> 2000 range which seems a bit silly.
> Any particular reason for that?

I changed the driver to use 2KiB buffers for frames in the
1518 -> 2048 range (BSEX=0, LPE=1). This breaks however
as packets are not dropped that are larger than the max specified?
Instead they're scribbled into memory causing a lockup after a while.

I noticed in e1000_change_mtu() that adapter->hw.max_frame_size
is only set after e1000_down();e1000_up(); Is that correct?

Are there any anwsers for the general questions I had even?

1. Is there a public dev tree available for the e1000 driver?
2. Are there programming docs for the various GigE chipsets?

thanks,
Pádraig.

       reply	other threads:[~2004-06-23 17:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <40D883C2.7010106@draigBrady.com>
2004-06-23 17:35 ` P [this message]
2004-06-24  5:49   ` TCP receiver's window calculation problem Cheng Jin
2004-06-24 17:43     ` John Heffner
2004-06-24 19:18       ` Cheng Jin
2004-06-24 19:26         ` John Heffner
2004-06-25  6:37           ` Cheng Jin
2004-06-25 13:43             ` John Heffner
     [not found]   ` <41b516cb040623114825a9c555@mail.gmail.com>
2004-06-24 10:36     ` [E1000-devel] e1000 jumbo problems P
2004-07-01 19:51     ` [PATCH] " P

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=40D9BF6B.4050807@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --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).