From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: David L Stevens <david.stevens@oracle.com>,
David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] sunvnet: generate ICMP PTMUD messages for smaller port MTUs
Date: Sat, 13 Sep 2014 23:19:43 +0300 [thread overview]
Message-ID: <5414A6DF.1060301@cogentembedded.com> (raw)
In-Reply-To: <5413723C.7040607@oracle.com>
Hello.
On 9/13/2014 1:22 AM, David L Stevens wrote:
> This patch sends ICMP and ICMPv6 messages for Path MTU Discovery when a remote
> port MTU is smaller than the device MTU. This allows mixing newer VIO protocol
> devices that support MTU negotiation with older devices that do not on the
> same vswitch. It also allows Linux-Linux LDOMs to use 64K-1 data packets even
> though Solaris vswitch is limited to <16K MTU.
> Signed-off-by: David L Stevens <david.stevens@oracle.com>
> ---
> drivers/net/ethernet/sun/sunvnet.c | 35 +++++++++++++++++++++++++++++++++++
> 1 files changed, 35 insertions(+), 0 deletions(-)
> diff --git a/drivers/net/ethernet/sun/sunvnet.c b/drivers/net/ethernet/sun/sunvnet.c
> index b557ec4..1251603 100644
> --- a/drivers/net/ethernet/sun/sunvnet.c
> +++ b/drivers/net/ethernet/sun/sunvnet.c
> @@ -17,6 +17,13 @@
> #include <linux/mutex.h>
> #include <linux/if_vlan.h>
> +#if IS_ENABLED(CONFIG_IPV6)
Patch spoiled as well...
> +#include <linux/icmpv6.h>
> +#endif
> +
> +#include <net/icmp.h>
> +#include <net/route.h>
> +
> #include <asm/vio.h>
> #include <asm/ldc.h>
WBR, Sergei
next prev parent reply other threads:[~2014-09-13 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 22:22 [PATCH net-next 3/3] sunvnet: generate ICMP PTMUD messages for smaller port MTUs David L Stevens
2014-09-12 22:26 ` David Miller
2014-09-13 20:19 ` Sergei Shtylyov [this message]
2014-09-14 2:18 ` 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=5414A6DF.1060301@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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).