From: Ilya Matveychikov <matvejchikov@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>, "Hu, Jiayu" <jiayu.hu@intel.com>
Subject: Re: [dpdk-dev] A question about GRO neighbor packet matching
Date: Thu, 7 Dec 2017 11:04:08 +0400 [thread overview]
Message-ID: <691D18D3-F11B-4F23-B4E6-35DB4F196257@gmail.com> (raw)
In-Reply-To: <20171206170157.1d839de0@xeon-e3>
> On Dec 7, 2017, at 5:01 AM, Stephen Hemminger <stephen@networkplumber.org> wrote:
>
> Ok, went RFC hunting and the relevant one seems to be RFC 6864.
> It mandates unique id's for each datagram so TCP does send them.
>
>
Thanks for mention such the RFC, never heard about it.
next prev parent reply other threads:[~2017-12-07 7:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 14:02 Ilya Matveychikov
2017-12-06 18:12 ` Stephen Hemminger
2017-12-06 18:38 ` Ilya Matveychikov
2017-12-06 23:15 ` Stephen Hemminger
2017-12-07 0:19 ` Ananyev, Konstantin
2017-12-07 1:01 ` Stephen Hemminger
2017-12-07 7:04 ` Ilya Matveychikov [this message]
2017-12-07 8:31 ` Hu, Jiayu
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=691D18D3-F11B-4F23-B4E6-35DB4F196257@gmail.com \
--to=matvejchikov@gmail.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=stephen@networkplumber.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).