All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Joyce Kong <joyce.kong@arm.com>,
	Ruifeng Wang <ruifeng.wang@arm.com>,
	"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "nd@arm.com" <nd@arm.com>
Subject: RE: [PATCH v1] net/i40e: add flow mark capability to NEON vector routine
Date: Tue, 15 Feb 2022 08:03:21 +0000	[thread overview]
Message-ID: <93f77ba5b31f4d73837c6741c9a36503@intel.com> (raw)
In-Reply-To: <20211217053601.776086-1-joyce.kong@arm.com>



> -----Original Message-----
> From: Joyce Kong <joyce.kong@arm.com>
> Sent: Friday, December 17, 2021 1:36 PM
> To: Ruifeng Wang <ruifeng.wang@arm.com>; Xing, Beilei
> <beilei.xing@intel.com>
> Cc: dev@dpdk.org; nd@arm.com; Joyce Kong <joyce.kong@arm.com>
> Subject: [PATCH v1] net/i40e: add flow mark capability to NEON vector routine
> 
> This commit adds a flow director support to i40e NEON vector RX path.
> 
> I40e can have 16 and 32 byte descriptors, and the Flow Director ID data and
> indication-bit are in different locations for each size descriptor. The support is
> implemented in two separate functions as they require vastly different
> operations.
> 
> The 16B descriptor re-purposes the "filter-status" u32 field to indicate FDIR ID
> when the FLM bit is set. No extra loads are required, however we do have to
> store to mbuf->fdir.hi, which is not stored to in the RX path before this patch.
> 
> The 32B descriptor requires loading the 2nd 16 bytes of each descriptor, to get
> the FLEXBH_STAT and FD Filter ID from qword3. The resulting data must also be
> stored to
> mbuf->fdir.hi, same as the 16B code path.
> 
> Signed-off-by: Joyce Kong <joyce.kong@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>

Applied to dpdk-next-net-intel.

Thanks
Qi


      reply	other threads:[~2022-02-15  8:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17  5:36 [PATCH v1] net/i40e: add flow mark capability to NEON vector routine Joyce Kong
2022-02-15  8:03 ` 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:
  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=93f77ba5b31f4d73837c6741c9a36503@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=joyce.kong@arm.com \
    --cc=nd@arm.com \
    --cc=ruifeng.wang@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.