From: Benjamin LaHaise <bcrl@redhat.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Paul P Komkoff Jr <i@stingr.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MTU vlan-related patch for tulip (2.4.x)
Date: Mon, 10 Dec 2001 17:37:11 -0500 [thread overview]
Message-ID: <20011210173710.C3323@redhat.com> (raw)
In-Reply-To: <20011210225759.B11450@stingr.net> <3C15146D.BA780B43@mandrakesoft.com> <3C1515E6.9C6EC26@mandrakesoft.com> <3C15197C.7050708@candelatech.com>
In-Reply-To: <3C15197C.7050708@candelatech.com>; from greearb@candelatech.com on Mon, Dec 10, 2001 at 01:22:20PM -0700
On Mon, Dec 10, 2001 at 01:22:20PM -0700, Ben Greear wrote:
> I think Becker once told me that there was no need to increase
> the 1536 number (it is already plenty big, and has some extra space
> in it already)...
You are correct: standard ethernet packet size is 1500 + 6 + 6 + 4 if
the crc is included. Of course, some drivers use part of the memory
in the packet for the rx descriptor....
-ben
prev parent reply other threads:[~2001-12-10 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 19:57 [PATCH] MTU vlan-related patch for tulip (2.4.x) Paul P Komkoff Jr
2001-12-10 20:00 ` Jeff Garzik
2001-12-10 20:07 ` Jeff Garzik
2001-12-10 20:22 ` Ben Greear
2001-12-10 22:37 ` Benjamin LaHaise [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=20011210173710.C3323@redhat.com \
--to=bcrl@redhat.com \
--cc=greearb@candelatech.com \
--cc=i@stingr.net \
--cc=jgarzik@mandrakesoft.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