DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wang, Haiyue" <haiyue.wang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Yang, Qiming" <qiming.yang@intel.com>
Cc: "Guo, Junfeng" <junfeng.guo@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/ice: optimize the FlexiMD hardware check
Date: Mon, 31 Aug 2020 03:53:27 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E706115522E1A8@SHSMSX107.ccr.corp.intel.com> (raw)
In-Reply-To: <20200812005753.467362-1-haiyue.wang@intel.com>

> -----Original Message-----
> From: Wang, Haiyue <haiyue.wang@intel.com>
> Sent: Wednesday, August 12, 2020 8:58 AM
> To: dev@dpdk.org; Yang, Qiming <qiming.yang@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>
> Cc: Guo, Junfeng <junfeng.guo@intel.com>; Wang, Haiyue
> <haiyue.wang@intel.com>
> Subject: [PATCH v2] net/ice: optimize the FlexiMD hardware check
> The Flexible Metadata #4 and #5 in the Rx Flex Descriptor are defined to
> extract the protocol specified fields or its offset. Its function relays on the DDP
> package support in hardware.
> Optimize to only check the hardware support when the user specifies the
> 'proto_xtr' devargs. And not require all the types need to be support in
> hardware, otherwise if new protocol extraction type is introduced, it is hard to
> maintain the compatibility. Just check the type support in need.
> And the protocol IDs are 8 bits length, so the uint8_t is the right type to be
> used. Also introduce the 'opcode' variable to specify the metadata extraction
> type: it can be protocol fields or offset report.
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel.


      reply	other threads:[~2020-08-31  3:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11 15:20 [dpdk-dev] [PATCH v1] net/ice: optimize the Rx metadata " Haiyue Wang
2020-08-12  0:57 ` [dpdk-dev] [PATCH v2] net/ice: optimize the FlexiMD " Haiyue Wang
2020-08-31  3:53   ` Zhang, Qi Z [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=039ED4275CED7440929022BC67E706115522E1A8@SHSMSX107.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.com \
    --cc=junfeng.guo@intel.com \
    --cc=qiming.yang@intel.com \


* 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).