From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bridge@osdl.org, netdev@oss.sgi.com
Subject: Re: [PATCH 2.6] bridge -- support different MTU sizes
Date: Fri, 9 Jul 2004 16:45:32 -0700 [thread overview]
Message-ID: <20040709164532.22202ce2.davem@redhat.com> (raw)
In-Reply-To: <20040708104143.67210e39@dell_ss3.pdx.osdl.net>
On Thu, 8 Jul 2004 10:41:43 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> This patch adds support for different size MTU's to bridging.
> It is useful for bridging Ethernet's with jumbo frames, etc.
>
> The mtu of the bridge pseudo-device is maintained as the minimum
> of all the underlying ports. And when forwarding a frame through
> the bridge, it will drop the frame if the outgoing port's MTU
> is less than the frame size (as per 802 standard).
Looks fine, applied.
prev parent reply other threads:[~2004-07-09 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 17:41 [PATCH 2.6] bridge -- support different MTU sizes Stephen Hemminger
2004-07-09 23:45 ` David S. Miller [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=20040709164532.22202ce2.davem@redhat.com \
--to=davem@redhat.com \
--cc=bridge@osdl.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).