From: Stephen Hemminger <stephen@networkplumber.org>
To: Fredrik Markstrom <fredrik.markstrom@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH 0/2] net: Set maximum receive packet size on veth interfaces
Date: Tue, 9 May 2017 08:49:28 -0700 [thread overview]
Message-ID: <20170509084928.4cfcbda5@xeon-e3> (raw)
In-Reply-To: <20170509124439.45674-1-fredrik.markstrom@gmail.com>
On Tue, 9 May 2017 14:44:36 +0200
Fredrik Markstrom <fredrik.markstrom@gmail.com> wrote:
> Currently veth drops all packets larger then the mtu set on the receiving
> end of the pair. This is inconsistent with most hardware ethernet drivers.
There is no guarantee that packets larger than MTU + VLAN tag will be received
by hardware drivers. So why is this necessary for veth? What is your special
use case which makes this necessary?
next prev parent reply other threads:[~2017-05-09 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 12:44 [PATCH 0/2] net: Set maximum receive packet size on veth interfaces Fredrik Markstrom
2017-05-09 12:44 ` [PATCH 1/2] net: Added mtu parameter to dev_forward_skb calls Fredrik Markstrom
2017-05-10 11:47 ` kbuild test robot
2017-05-09 12:44 ` [PATCH 2/2] veth: Added attribute to set maximum receive size on veth interfaces Fredrik Markstrom
2017-05-09 12:44 ` Support for VETH_MRU in libnl Fredrik Markstrom
2017-05-09 15:49 ` Stephen Hemminger [this message]
2017-05-09 17:48 ` [PATCH 0/2] net: Set maximum receive packet size on veth interfaces David Miller
2017-05-10 0:38 ` Fredrik Markström
2017-05-10 0:42 ` Fredrik Markström
2017-05-12 3:27 ` Cong Wang
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=20170509084928.4cfcbda5@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=ast@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fredrik.markstrom@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).