From: Andrew Boyer <andrew.boyer@amd.com>
To: <web@dpdk.org>
Cc: Andrew Boyer <andrew.boyer@amd.com>
Subject: [PATCH] add supported AMD Pensando cryptodevs
Date: Mon, 3 Mar 2025 07:28:32 -0800 [thread overview]
Message-ID: <20250303152832.48160-1-andrew.boyer@amd.com> (raw)
These devices all have embedded cryptodev support.
Signed-off-by: Andrew Boyer <andrew.boyer@amd.com>
---
content/supported/cryptos/pensando.md | 7 +++++++
1 file changed, 7 insertions(+)
create mode 100644 content/supported/cryptos/pensando.md
diff --git a/content/supported/cryptos/pensando.md b/content/supported/cryptos/pensando.md
new file mode 100644
index 0000000..c4b64a3
--- /dev/null
+++ b/content/supported/cryptos/pensando.md
@@ -0,0 +1,7 @@
++++
+title = "AMD Pensando"
+description = "ionic"
+hidden = true
++++
+
+- [ionic](//doc.dpdk.org/guides/cryptodevs/ionic.html) (DSC-25, DSC-100, DSC2-200, DSC3-400)
--
2.17.1
next reply other threads:[~2025-03-03 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 15:28 Andrew Boyer [this message]
2025-03-03 16:33 ` 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=20250303152832.48160-1-andrew.boyer@amd.com \
--to=andrew.boyer@amd.com \
--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).