From: Patrick McHardy <kaber@trash.net>
To: Vlad Yasevich <vyasevic@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC PATCH] vlan: Try to adjust lower device mtu when configuring 802.1AD vlans
Date: Wed, 2 Apr 2014 14:21:21 +0200 [thread overview]
Message-ID: <20140402122121.GD26334@macbook.localnet> (raw)
In-Reply-To: <1396387054-4510-1-git-send-email-vyasevic@redhat.com>
On Tue, Apr 01, 2014 at 05:17:34PM -0400, Vlad Yasevich wrote:
> 802.1AD vlans supposed to encapsulate 802.1Q vlans. To
> do this, we need an extra 4 bytes of header which are typically
> not accounted for by lower devices. Some devices can not
> support frames longer then 1522 bytes at all. Such devices
> can not really support 802.1AD, even in software, without
> the vlan reducing its mtu value.
>
> This patch propses to increate the lower devices MTU to 1504
> in case of 802.1AD configuration, and if device doesn't
> support it, fail the creation of the vlan. The user has an
> option to configure older-style Q-in-Q vlans and manually
> lower the mtu to support such encapsulation.
I think you should do the opposite. The lower layer device may be used
for other things than the VLAN, so it doesn't seem right to change it's
MTU. Instead I'd propose to set the MTU of the 802.1ad VLAN device to
the lower device'e MTU - 4 unless a MTU has been specified by the user.
BTW, I couldn't find anything related to MTU handling in the 802.1ad
standard, however I only have an old copy and might have looked in the
wrong place. Do you have any information how this is supposed to be
handled?
next prev parent reply other threads:[~2014-04-02 12:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 21:17 [RFC PATCH] vlan: Try to adjust lower device mtu when configuring 802.1AD vlans Vlad Yasevich
2014-04-01 21:34 ` Florian Fainelli
2014-04-02 12:21 ` Patrick McHardy [this message]
2014-04-02 13:31 ` Vlad Yasevich
2014-04-02 16:37 ` Toshiaki Makita
2014-04-02 16:44 ` Vlad Yasevich
2014-04-03 8:32 ` Toshiaki Makita
2014-04-03 13:07 ` Vlad Yasevich
2014-04-04 15:08 ` Toshiaki Makita
2014-04-04 15:22 ` Vlad Yasevich
2014-04-06 15:21 ` Toshiaki Makita
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=20140402122121.GD26334@macbook.localnet \
--to=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.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;
as well as URLs for NNTP newsgroup(s).