From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kirill Rybalchenko <kirill.rybalchenko@intel.com>, dev@dpdk.org
Cc: andrey.chilikin@intel.com, beilei.xing@intel.com, jingjing.wu@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] net/i40e: add support for packet template to flow director
Date: Tue, 24 Oct 2017 11:02:55 -0700 [thread overview]
Message-ID: <8fcac4d4-a0e3-db4c-d496-2c29f833c983@intel.com> (raw)
In-Reply-To: <1508854093-26371-1-git-send-email-kirill.rybalchenko@intel.com>
On 10/24/2017 7:08 AM, Kirill Rybalchenko wrote:
> For complex packets use raw flow type with pre-constructed packet buffer
> instead of creating a packet internally in PMD.
>
> v2:
>
> Fix documentation according to doxygen style comments.
> Fix compilation warnings for clang target.
>
> Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2017-10-24 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 9:00 [dpdk-dev] [PATCH] " Kirill Rybalchenko
2017-10-23 22:11 ` Ferruh Yigit
2017-10-24 14:08 ` [dpdk-dev] [PATCH v2] " Kirill Rybalchenko
2017-10-24 18:02 ` Ferruh Yigit [this message]
2017-10-24 18:07 ` Ferruh Yigit
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=8fcac4d4-a0e3-db4c-d496-2c29f833c983@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrey.chilikin@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=kirill.rybalchenko@intel.com \
/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).