From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Guo, Jia" <jia.guo@intel.com>, "Zhang, Helin" <helin.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] drivers/i40e: Add new PCTYPE for x722 hardware driver
Date: Mon, 5 Sep 2016 05:44:01 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F80E1C2653@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1472203505-76527-1-git-send-email-jia.guo@intel.com>
> -----Original Message-----
> From: Guo, Jia
> Sent: Friday, August 26, 2016 5:25 PM
> To: Zhang, Helin; Wu, Jingjing
> Cc: dev@dpdk.org; Guo, Jia
> Subject: [PATCH] drivers/i40e: Add new PCTYPE for x722 hardware driver
>
> There are 6 new PCTYPE be enabled in the i40e hardware driver for x722, add
Mini comments :
How about "There are 6 new PCTYEs enabled in device X722. This patch ......"
> them to let user to use it to filter the corresponding PCTYPE packet in x722.
>
> The new PCTYPE As bellow:
> NonF Unicast IPv4, UDP
> NonF Multicast IPv4, UDP
> NonF IPv4, TCP, SYN, no ACK
> NonF Unicast IPv6, UDP
> NonF Multicast IPv6, UDP
Actually, the new PCTYPE are not exposed to user in DPDK. Please not how
You deal with them.
next prev parent reply other threads:[~2016-09-05 5:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 9:25 Jeff Guo
2016-08-26 9:25 ` [dpdk-dev] [PATCH] drivers/i40e: Add FD PCTYPE translation for x722 Jeff Guo
2016-09-05 5:40 ` Wu, Jingjing
2016-09-07 9:38 ` [dpdk-dev] [PATCH v2 2/2] drivers/i40e: Add FD PCTYPE translation for device x722 Jeff Guo
2016-09-08 2:25 ` Wu, Jingjing
2016-09-19 14:57 ` Bruce Richardson
2016-09-05 5:44 ` Wu, Jingjing [this message]
2016-09-07 9:38 ` [dpdk-dev] [PATCH v2 1/2] drivers/i40e: Add new PCTYPEs " Jeff Guo
2016-09-08 2:24 ` Wu, Jingjing
2016-09-19 14:56 ` Bruce Richardson
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=9BB6961774997848B5B42BEC655768F80E1C2653@SHSMSX103.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jia.guo@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).