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 1/3] net/idpf: add support for CPF
Date: Mon, 26 Sep 2022 16:42:46 +0800 [thread overview]
Message-ID: <20220926084248.1421987-2-junfeng.guo@intel.com> (raw)
In-Reply-To: <20220926084248.1421987-1-junfeng.guo@intel.com>
Add CPF device id in idpf map.
Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
---
drivers/net/idpf/idpf_ethdev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/idpf/idpf_ethdev.c b/drivers/net/idpf/idpf_ethdev.c
index b3ca4e3326..08ada728b1 100644
--- a/drivers/net/idpf/idpf_ethdev.c
+++ b/drivers/net/idpf/idpf_ethdev.c
@@ -1193,6 +1193,7 @@ idpf_dev_uninit(struct rte_eth_dev *dev)
static const struct rte_pci_id pci_id_idpf_map[] = {
{ RTE_PCI_DEVICE(IECM_INTEL_VENDOR_ID, IECM_DEV_ID_PF) },
+ { RTE_PCI_DEVICE(IECM_INTEL_VENDOR_ID, IECM_DEV_ID_CPF) },
{ .vendor_id = 0, /* sentinel */ },
};
--
2.25.1
next prev parent reply other threads:[~2022-09-26 8:43 UTC|newest]
Thread overview: 8+ 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 ` [RFC v2 0/3] enable hairpin queue Junfeng Guo
2022-09-26 8:42 ` Junfeng Guo [this message]
2022-09-26 8:42 ` [RFC v2 2/3] net/idpf: add support for " Junfeng Guo
2022-09-26 8:42 ` [RFC v2 3/3] net/idpf: adjust RSS LUT to exclude " Junfeng Guo
2022-09-05 11:30 ` [RFC 2/3] net/idpf: add support for " 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-2-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 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).