public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Wyckoff <pw@osc.edu>
To: John Weidman <johnw@believe.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is jumbo ethernet MTU possible with Hamachi Gigabit ethernet driver?
Date: Thu, 5 Apr 2001 10:36:41 -0400	[thread overview]
Message-ID: <20010405103641.B11386@quasar.osc.edu> (raw)
In-Reply-To: <3ACBC361.CA701A2D@believe.com>
In-Reply-To: <3ACBC361.CA701A2D@believe.com>; from johnw@believe.com on Wed, Apr 04, 2001 at 05:59:13PM -0700

The hardware also must support jumbo MTUs.  Hamachi limit is 1518 or
1522 (vlan) bytes, and the driver can't fix that.

		-- Pete

johnw@believe.com said:
> I'm trying to get some Gigabit ethernet cards that use the Packet
> Engines Hamachi GNIC-II chip to use a large mtu to attempt to get a
> throughput of close to the 1Gb rating of the card.  This is on a Compact
> PCI Alpha system.  I'm trying to use an MTU in the 8000 to 9000 range
> and so far have not been able to get these MTUs to work.
> 
> I have changed the PKT_BUF_SZ and MAX_FRAME_SIZE constants in hamachi.c
> and ETH_DATA_LEN and ETH_FRAME_LEN in if_ether.h.  I can use ifconfig to
> change the MTU above 1500 on one side of a connection but as soon as I
> raise the MTU on both sides to greater than 1500 the link dies.  I can
> change the MTU with ifconfig back to 1500 and the link will resume
> operation.  We are currently somewhat married to the 2.2.14 kernel.
> 
> I read that some ethernet drivers will support jumbo MTUs.  There
> appears to be something in the hamachi driver or the kernel that I've
> missed.  Perhaps this only works with a later version kernel or the
> hamachi driver needs more changes?  Any help would be appreciated.

      reply	other threads:[~2001-04-05 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-05  0:59 Is jumbo ethernet MTU possible with Hamachi Gigabit ethernet driver? John Weidman
2001-04-05 14:36 ` Pete Wyckoff [this message]

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=20010405103641.B11386@quasar.osc.edu \
    --to=pw@osc.edu \
    --cc=johnw@believe.com \
    --cc=linux-kernel@vger.kernel.org \
    /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