From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com
Subject: Re: [PATCH 00/10] support rte_flow for flower firmware with NFDk
Date: Wed, 7 Jun 2023 15:23:06 +0100 [thread overview]
Message-ID: <82d70ea6-a595-5f69-2fcb-6f61ac17b4a5@amd.com> (raw)
In-Reply-To: <20230607015709.336420-1-chaoyong.he@corigine.com>
On 6/7/2023 2:56 AM, Chaoyong He wrote:
> This patch series add the support of rte_flow for card which using
> flower firmware with NFDk:
> 1. Fix the underlying API logic to support this feature.
> 2. Import a unified check and dispatch layer for different versions of NFD.
> 3. Refactor the meta data logic to adapt this dispatch layer.
> 4. Refactor the packet receive logic to adapt this dispatch layer.
> 5. Refactor the packet transmit logic to adapt this dispatch layer.
> 6. Merge the logics of representor port to decrease the redundancy logic.
>
> Chaoyong He (10):
> net/nfp: fix the problem of rtsym
> net/nfp: add a check function for the NFD version
> net/nfp: refactor the insert metadata logic of NFD3
> net/nfp: add the insert metadata logic of NFDk
> net/nfp: add a dispatch layer for Tx function of ctrl VNIC
> net/nfp: add the xmit function of NFDk for ctrl VNIC
> net/nfp: add a dispatch layer for Tx function of representor
> net/nfp: merge the xmit function of NFD3
> net/nfp: add the xmit function of NFDk for PF representor
> net/nfp: merge the recv function
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-06-07 14:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 1:56 Chaoyong He
2023-06-07 1:57 ` [PATCH 01/10] net/nfp: fix the problem of rtsym Chaoyong He
2023-06-07 1:57 ` [PATCH 02/10] net/nfp: add a check function for the NFD version Chaoyong He
2023-06-07 1:57 ` [PATCH 03/10] net/nfp: refactor the insert metadata logic of NFD3 Chaoyong He
2023-06-07 1:57 ` [PATCH 04/10] net/nfp: add the insert metadata logic of NFDk Chaoyong He
2023-06-07 1:57 ` [PATCH 05/10] net/nfp: add a dispatch layer for Tx function of ctrl VNIC Chaoyong He
2023-06-07 1:57 ` [PATCH 06/10] net/nfp: add the xmit function of NFDk for " Chaoyong He
2023-06-07 1:57 ` [PATCH 07/10] net/nfp: add a dispatch layer for Tx function of representor Chaoyong He
2023-06-07 1:57 ` [PATCH 08/10] net/nfp: merge the xmit function of NFD3 Chaoyong He
2023-06-07 1:57 ` [PATCH 09/10] net/nfp: add the xmit function of NFDk for PF representor Chaoyong He
2023-06-07 1:57 ` [PATCH 10/10] net/nfp: merge the recv function Chaoyong He
2023-06-07 14:23 ` Ferruh Yigit [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=82d70ea6-a595-5f69-2fcb-6f61ac17b4a5@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.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).