From: YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>
To: Alan Davey <Alan.Davey@metaswitch.com>,
David Miller <davem@davemloft.net>
Cc: hideaki.yoshifuji@miraclelinux.com,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"kuznet@ms2.inr.ac.ru" <kuznet@ms2.inr.ac.ru>,
"jmorris@namei.org" <jmorris@namei.org>,
"yoshfuji@linux-ipv6.org" <yoshfuji@linux-ipv6.org>,
"kaber@trash.net" <kaber@trash.net>
Subject: Re: [PATCH] net: Fragment large datagrams even when IP_HDRINCL is set.
Date: Wed, 8 Jun 2016 18:33:13 +0900 [thread overview]
Message-ID: <5757E659.9070501@miraclelinux.com> (raw)
In-Reply-To: <BN3PR0201MB1059316BEC3EC7F6CBF2F0E4F95E0@BN3PR0201MB1059.namprd02.prod.outlook.com>
Hi
Please do not use "top-posting" here.
Alan Davey wrote:
> Hi David
>
> Thank you for your email. I understand raw IP sockets have worked this way for a long time, but I think that there is real benefit in this patch for little risk. Please take a look at the following and let me know what you think.
>
> - The current behaviour is counter-intuitive (fragmentation takes place in all other cases) and therefore different to what everyone expects.
I do NEVER expect fragmentation occurs with IP_HDRINCL, at least.
--
Hideaki Yoshifuji <hideaki.yoshifuji@miraclelinux.com>
Technical Division, MIRACLE LINUX CORPORATION
next prev parent reply other threads:[~2016-06-08 9:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 14:23 [PATCH] net: Fragment large datagrams even when IP_HDRINCL is set Alan Davey
2016-05-31 18:39 ` David Miller
2016-06-08 8:41 ` Alan Davey
2016-06-08 9:33 ` YOSHIFUJI Hideaki [this message]
2016-06-08 9:39 ` Paul Jakma
2016-06-08 17:25 ` David Miller
2016-06-15 10:41 ` Alan Davey
2016-07-08 12:55 ` Paul Jakma
2016-07-08 22:41 ` David Miller
2016-07-08 23:21 ` Alexey Kuznetsov
2016-07-12 12:34 ` Alan Davey
2016-07-12 18:11 ` David Miller
2021-12-14 12:03 ` Senthil Kumar Nagappan
2016-06-15 13:03 ` Hannes Frederic Sowa
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=5757E659.9070501@miraclelinux.com \
--to=hideaki.yoshifuji@miraclelinux.com \
--cc=Alan.Davey@metaswitch.com \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 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.