From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: David L Stevens <david.stevens@oracle.com>,
David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCHv3 net-next 2/3] sunvnet: allow admin to set sunvnet MTU
Date: Sun, 14 Sep 2014 08:21:09 -0400 [thread overview]
Message-ID: <54158835.8000508@oracle.com> (raw)
In-Reply-To: <5414FA4D.6030504@oracle.com>
On 09/13/2014 10:15 PM, David L Stevens wrote:
> I wouldn't say I like it, either, but the problem is that without it, we
> are tied to the least common denominator. Anything that doesn't support
> v1.6 of the VIO protocol is stuck at the low MTU and low throughput, and
To put things in perspective, in practice its only legacy linux today
that will do the v1.0, and administrators are likely to want to upgrade
to the later version, so encumbering the code with legacy version
support may end up becoming hard-to-maintain code?
> I think of it as an Ethernet connected to a virtual switch, and the ICMP
> errors are for PMTUD are analogous to IGMP snooping. This is not an Ethernet
> device alone-- those don't negotiate per-destination link MTUs. But nothing forces
> anyone to mix MTUs; the ICMP errors simply allow it.
As I understand it, this method of sending ICMP from the driver will not
work for L2 (non-IP) packets, and it will not even work for IP packets
that are coming to us, from, say, openvswitch, right? So in practice it
actually has limited usability?
--Sowmini
next prev parent reply other threads:[~2014-09-14 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 16:00 [PATCHv3 net-next 2/3] sunvnet: allow admin to set sunvnet MTU David L Stevens
2014-09-13 20:21 ` David Miller
2014-09-14 2:15 ` David L Stevens
2014-09-14 12:21 ` Sowmini Varadhan [this message]
2014-09-14 13:24 ` David L Stevens
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=54158835.8000508@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=davem@davemloft.net \
--cc=david.stevens@oracle.com \
--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).