mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Robert PipCA <robertpipca@yahoo.com>
Cc: vortex@scyld.com, linux-kernel@vger.kernel.org
Subject: Re: MTU discovery
Date: Mon, 10 Jun 2002 11:05:13 +0300	[thread overview]
Message-ID: <20020610110513.I18899@mea-ext.zmailer.org> (raw)
In-Reply-To: <20020610074507.69402.qmail@web21301.mail.yahoo.com>

On Mon, Jun 10, 2002 at 12:45:07AM -0700, Robert PipCA wrote:
>   Hi,
>   I'm working on a project that require knowing the max MTU size
> supported by the 3Com PCI 3c905C (Boomerang).
> The datasheet provided by 3Com does not mention it, and I already
> did the usual google search, but didn't find it neither.
> Does anyone knows a "generic way" of knowing this (or chip-specific)?

  Oh, it is mentioned there, although not with that name.

  The Ethernet Standard (IEEE 802.3) specifies that the frame size
  shall be 1500 octets.   That is the NORMAL CASE max MTU value for
  all ethernet devices.

  Some devices do, however, support reception (and transmit) of what
  is called "jumbograms".  With boomerang you can set a register
  to contain the limit value.  Alternatively with boomerang, and
  its predecessors, you can set a bit to accept extra-large frames.

  I recall the ultimate limit is in order of 4kB.

>   Thanks in advance.
> --Robert

/Matti Aarnio

  reply	other threads:[~2002-06-10  8:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-10  7:45 Robert PipCA
2002-06-10  8:05 ` Matti Aarnio [this message]
2002-06-10  8:23   ` Robert PipCA
2002-06-10  9:50   ` Olivier Galibert
2002-06-10 21:45     ` Bill Davidsen
2002-06-10 22:02       ` Joel Jaeggli
2002-06-11  3:31         ` BALBIR SINGH
2002-06-11  3:46           ` Joel Jaeggli
2002-06-11 19:27   ` [vortex] " Donald Becker
2002-06-12  0:57     ` Jeff Garzik

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=20020610110513.I18899@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robertpipca@yahoo.com \
    --cc=vortex@scyld.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

all inboxes | Powered by JetHome®