From: Junfeng Guo <junfeng.guo@intel.com>
To: qi.z.zhang@intel.com, jingjing.wu@intel.com, beilei.xing@intel.com
Cc: dev@dpdk.org, xiao.w.wang@intel.com, junfeng.guo@intel.com
Subject: [RFC v2 0/3] enable hairpin queue
Date: Mon, 26 Sep 2022 16:42:45 +0800 [thread overview]
Message-ID: <20220926084248.1421987-1-junfeng.guo@intel.com> (raw)
In-Reply-To: <20220905113031.3223290-2-junfeng.guo@intel.com>
This patchset enables CPF for Intel Device ID of 0x1453 and supports
hairpin queue based on idpf (Infrastructure Data Path Function) PMD
[*EXPERIMENTAL*] in DPDK.
This patchset is based on the idpf PMD code:
https://patchwork.dpdk.org/project/dpdk/list/?series=24538&state=*
v2:
fix hairpin queue config sequence issue.
Junfeng Guo (3):
net/idpf: add support for CPF
net/idpf: add support for hairpin queue
net/idpf: adjust RSS LUT to exclude hairpin queue
drivers/net/idpf/base/virtchnl2.h | 6 +
drivers/net/idpf/idpf_ethdev.c | 206 +++++++++++-
drivers/net/idpf/idpf_ethdev.h | 5 +
drivers/net/idpf/idpf_rxtx.c | 521 ++++++++++++++++++++++++++++--
drivers/net/idpf/idpf_rxtx.h | 27 ++
drivers/net/idpf/idpf_vchnl.c | 211 +++++++++---
6 files changed, 896 insertions(+), 80 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2022-09-26 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 11:30 [RFC 0/3] enable hairpin queue Junfeng Guo
2022-09-05 11:30 ` [RFC 1/3] net/idpf: add support for CPF Junfeng Guo
2022-09-26 8:42 ` Junfeng Guo [this message]
2022-09-26 8:42 ` [RFC v2 " Junfeng Guo
2022-09-26 8:42 ` [RFC v2 2/3] net/idpf: add support for hairpin queue Junfeng Guo
2022-09-26 8:42 ` [RFC v2 3/3] net/idpf: adjust RSS LUT to exclude " Junfeng Guo
2024-10-02 16:41 ` [RFC 1/3] net/idpf: add support for CPF Stephen Hemminger
2022-09-05 11:30 ` [RFC 2/3] net/idpf: add support for hairpin queue Junfeng Guo
2022-09-05 11:30 ` [RFC 3/3] net/idpf: adjust RSS LUT to exclude " Junfeng Guo
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=20220926084248.1421987-1-junfeng.guo@intel.com \
--to=junfeng.guo@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=xiao.w.wang@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 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.