From: Patrick McHardy <kaber@trash.net>
To: Joe Stringer <joestringer@nicira.com>
Cc: netdev@vger.kernel.org, Pablo Neira Ayuso <pablo@netfilter.org>,
Andy Zhou <azhou@nicira.com>,
linux-kernel@vger.kernel.org, Justin Pettit <jpettit@nicira.com>,
Thomas Graf <tgraf@suug.ch>
Subject: Re: [RFCv2 net-next 6/7] net: Refactor ip_defrag() APIs
Date: Tue, 3 Mar 2015 08:20:54 +0000 [thread overview]
Message-ID: <20150303082054.GA11110@acer.localdomain> (raw)
In-Reply-To: <1425333305-19702-7-git-send-email-joestringer@nicira.com>
On 02.03, Joe Stringer wrote:
> From: Andy Zhou <azhou@nicira.com>
>
> Currently, ip_defrag() does not keep track of the maximum fragmentation
> size for each fragmented packet. This information is not necessary since
> current Linux IP fragmentation always fragments a packet based on output
> devices' MTU.
It does, search for max_size.
next prev parent reply other threads:[~2015-03-03 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 21:54 [RFCv2 net-next 0/7] OVS conntrack support Joe Stringer
2015-03-02 21:54 ` [RFCv2 net-next 1/7] openvswitch: Serialize acts with original netlink len Joe Stringer
2015-03-02 21:55 ` [RFCv2 net-next 2/7] openvswitch: Move MASKED* macros to datapath.h Joe Stringer
2015-03-02 21:55 ` [RFCv2 net-next 3/7] openvswitch: Add conntrack action Joe Stringer
2015-03-02 21:55 ` [RFCv2 net-next 4/7] openvswitch: Allow matching on conntrack mark Joe Stringer
2015-03-02 21:55 ` [RFCv2 net-next 5/7] net: refactor ip_fragment() Joe Stringer
2015-03-02 21:55 ` [RFCv2 net-next 6/7] net: Refactor ip_defrag() APIs Joe Stringer
2015-03-03 8:20 ` Patrick McHardy [this message]
2015-03-03 19:55 ` Andy Zhou
2015-03-02 21:55 ` [RFCv2 net-next 7/7] openvswitch: Support fragmented IPv4 packets for conntrack Joe Stringer
2015-03-03 0:59 ` [RFCv2 net-next 0/7] OVS conntrack support Tom Herbert
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=20150303082054.GA11110@acer.localdomain \
--to=kaber@trash.net \
--cc=azhou@nicira.com \
--cc=joestringer@nicira.com \
--cc=jpettit@nicira.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tgraf@suug.ch \
/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).