From: Junfeng Guo <junfeng.guo@intel.com>
To: thomas@monjalon.net, ferruh.yigit@amd.com
Cc: web@dpdk.org, Junfeng Guo <junfeng.guo@intel.com>
Subject: [PATCH] add Intel gve to supported NICs
Date: Fri, 28 Oct 2022 14:34:17 +0800 [thread overview]
Message-ID: <20221028063417.2681699-1-junfeng.guo@intel.com> (raw)
Note that this driver is for gVNIC on Google Cloud Platform.
And this driver is added at DPDK 22.11 release.
Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
---
content/supported/nics/intel.md | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/content/supported/nics/intel.md b/content/supported/nics/intel.md
index 22ec2e9..dafe634 100644
--- a/content/supported/nics/intel.md
+++ b/content/supported/nics/intel.md
@@ -1,6 +1,6 @@
+++
title = "Intel"
-description = "e1000, ixgbe, i40e, ice, fm10k, ipn3ke, ifc, igc"
+description = "e1000, ixgbe, i40e, ice, fm10k, gve, ipn3ke, ifc, igc"
hidden = true
+++
@@ -12,9 +12,12 @@ hidden = true
- [i40e](//doc.dpdk.org/guides/nics/i40e.html) (X710, XL710, X722, XXV710)
- [ice](//doc.dpdk.org/guides/nics/ice.html) (E810)
- [fm10k](//doc.dpdk.org/guides/nics/fm10k.html) (FM10420)
+- [gve](//doc.dpdk.org/guides/nics/gve.html) (gVNIC)
- [ipn3ke](//doc.dpdk.org/guides/nics/ipn3ke.html) (PAC N3000)
- [ifc](//doc.dpdk.org/guides/vdpadevs/ifc.html) (IFC)
{{% notice note %}}
-Note: The drivers e1000 and e1000e are also called em. The drivers em and igb are sometimes grouped in e1000 family.
+- The drivers e1000 and e1000e are also called em.
+- The drivers em and igb are sometimes grouped in e1000 family.
+- The driver gve is for gVNIC on Google Cloud Platform.
{{% /notice %}}
--
2.34.1
next reply other threads:[~2022-10-28 6:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 6:34 Junfeng Guo [this message]
2022-10-28 9:12 ` Thomas Monjalon
2022-10-28 9:28 ` Guo, Junfeng
2022-10-28 9:31 ` [PATCH v2] add Google " Junfeng Guo
2022-11-09 20:01 ` Thomas Monjalon
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=20221028063417.2681699-1-junfeng.guo@intel.com \
--to=junfeng.guo@intel.com \
--cc=ferruh.yigit@amd.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
/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).