From: David Miller <davem@davemloft.net>
To: 3chas3@gmail.com
Cc: netdev@vger.kernel.org, stephen@networkplumber.org
Subject: Re: [PATCH net-next] bridge: Allow max MTU when multiple VLANs present
Date: Fri, 23 Mar 2018 12:17:47 -0400 (EDT) [thread overview]
Message-ID: <20180323.121747.2120157916968005999.davem@davemloft.net> (raw)
In-Reply-To: <20180322153406.17760-1-3chas3@gmail.com>
From: Chas Williams <3chas3@gmail.com>
Date: Thu, 22 Mar 2018 11:34:06 -0400
> If the bridge is allowing multiple VLANs, some VLANs may have
> different MTUs. Instead of choosing the minimum MTU for the
> bridge interface, choose the maximum MTU of the bridge members.
> With this the user only needs to set a larger MTU on the member
> ports that are participating in the large MTU VLANS.
>
> Signed-off-by: Chas Williams <3chas3@gmail.com>
Applied, thanks.
next prev parent reply other threads:[~2018-03-23 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 15:34 [PATCH net-next] bridge: Allow max MTU when multiple VLANs present Chas Williams
2018-03-22 20:21 ` Nikolay Aleksandrov
2018-03-23 4:53 ` Roopa Prabhu
2018-03-29 16:49 ` Roopa Prabhu
2018-03-30 1:02 ` Toshiaki Makita
2018-03-30 19:54 ` Chas Williams
2018-04-02 15:08 ` Roopa Prabhu
2018-04-02 15:26 ` Chas Williams
2018-04-03 6:13 ` Roopa Prabhu
2018-04-03 10:14 ` Chas Williams
2018-03-23 16:17 ` David Miller [this message]
2018-03-23 16:20 ` Nikolay Aleksandrov
2018-03-23 21:50 ` Chas Williams
2018-03-23 16:27 ` [PATCH net-next] net: bridge: fix direct access to bridge vlan_enabled and use helper Nikolay Aleksandrov
2018-03-23 16:41 ` David Miller
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=20180323.121747.2120157916968005999.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=3chas3@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).