From: Stephen Hemminger <stephen@networkplumber.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Guillaume Nault <gnault@redhat.com>,
Kees Cook <keescook@chromium.org>,
Eric Dumazet <edumazet@google.com>,
"Ziyang Xuan (William)" <william.xuanziyang@huawei.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Vasily Averin <vvs@virtuozzo.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] net: vlan: allow vlan device MTU change follow real device from smaller to bigger
Date: Wed, 23 Feb 2022 09:05:02 -0800 [thread overview]
Message-ID: <20220223090502.29e5f87a@hermes.local> (raw)
In-Reply-To: <20220223080342.5cdd597c@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Wed, 23 Feb 2022 08:03:42 -0800
Jakub Kicinski <kuba@kernel.org> wrote:
> On Wed, 23 Feb 2022 12:26:18 +0100 Guillaume Nault wrote:
> > Do you mean something like:
> >
> > ip link set dev eth0 vlan-mtu-policy <policy-name>
> >
> > that'd affect all existing (and future) vlans of eth0?
>
> I meant
>
> ip link set dev vlan0 mtu-policy blah
>
> but also
>
> ip link set dev bond0 mtu-policy blah
>
> and
>
> ip link set dev macsec0 mtu-policy blah2
> ip link set dev vxlan0 mtu-policy blah2
Sorry, putting this in ip link is not the right place.
It belongs in sysctl (if at all); not convinced this is worth doing.
prev parent reply other threads:[~2022-02-23 17:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 12:46 [PATCH net] net: vlan: allow vlan device MTU change follow real device from smaller to bigger Ziyang Xuan
2022-02-21 15:43 ` Eric Dumazet
2022-02-22 0:58 ` Herbert Xu
2022-02-22 2:06 ` Ziyang Xuan (William)
2022-02-22 2:27 ` Eric Dumazet
2022-02-22 7:31 ` Ziyang Xuan (William)
2022-02-23 1:55 ` Ziyang Xuan (William)
2022-02-22 10:37 ` Guillaume Nault
2022-02-22 23:28 ` Jakub Kicinski
2022-02-23 11:26 ` Guillaume Nault
2022-02-23 15:17 ` Stephen Hemminger
2022-02-23 16:34 ` Guillaume Nault
2022-02-23 16:03 ` Jakub Kicinski
2022-02-23 16:58 ` Guillaume Nault
2022-02-23 17:37 ` Jakub Kicinski
2022-02-23 19:46 ` Guillaume Nault
2022-02-23 17:05 ` Stephen Hemminger [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=20220223090502.29e5f87a@hermes.local \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vvs@virtuozzo.com \
--cc=william.xuanziyang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.