From: David L Stevens <david.stevens@oracle.com>
To: Raghuram Kothakota <Raghuram.Kothakota@oracle.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCHv6 net-next 2/3] sunvnet: allow admin to set sunvnet MTU
Date: Thu, 18 Sep 2014 09:10:40 -0400 [thread overview]
Message-ID: <541AD9D0.2010007@oracle.com> (raw)
In-Reply-To: <C383AC6E-F0A2-4510-8EC6-0EC606870249@oracle.com>
On 09/18/2014 12:19 AM, Raghuram Kothakota wrote:
>
> FYI, LDoms manager provides the maximum MTU of packets allowed for
> a vnet device in the "virtual-device" MD node corresponding to the vnet device.
> The virtual switch is expected to enforce that size for packets that go through
> it. Ideally we want a Guest OS to honor that MTU setting as well, which is probably
> not the case here. LDoms manager doesn't allow setting more than 16K today,
> I guess this code is ignoring this for Guest to Guest communication.
Yes, this is negotiated per LDC connection, and it uses the switch size when using
the switch port, but can use a full 64K linux-linux. Anything involving Solaris will
be limited to 16000, and any connections to Legacy linux will be limited to 1500 bytes.
If the port for a particular destination changes and the new port has a smaller MTU,
the packets will trigger an ICMP PMTUD notification and any active connections will
continue to work at the smaller MTU, by PMTUD design.
+-DLS
prev parent reply other threads:[~2014-09-18 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 0:10 [PATCHv6 net-next 2/3] sunvnet: allow admin to set sunvnet MTU David L Stevens
2014-09-18 4:19 ` Raghuram Kothakota
2014-09-18 13:10 ` David L Stevens [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=541AD9D0.2010007@oracle.com \
--to=david.stevens@oracle.com \
--cc=Raghuram.Kothakota@oracle.com \
--cc=davem@davemloft.net \
--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).