From: Lijuan Tu <lijuan.tu@intel.com>
To: thomas@monjalon.net
Cc: web@dpdk.org, Lijuan Tu <lijuan.tu@intel.com>
Subject: [dpdk-web] [PATCH] add 21.05&21.02 Intel performance reports
Date: Sat, 11 Sep 2021 00:43:31 +0800 [thread overview]
Message-ID: <1631292211-50614-1-git-send-email-lijuan.tu@intel.com> (raw)
Signed-off-by: Lijuan Tu <lijuan.tu@intel.com>
---
content/perf-reports/_index.md | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/content/perf-reports/_index.md b/content/perf-reports/_index.md
index 83dea4e..0c06ea5 100644
--- a/content/perf-reports/_index.md
+++ b/content/perf-reports/_index.md
@@ -3,10 +3,20 @@ title = "Performance Reports"
weight = "7"
+++
+- [DPDK 21.05 Intel NIC Performance Report]
+ (//fast.dpdk.org/doc/perf/DPDK_21_05_Intel_NIC_performance_report.pdf)
+- [DPDK 21.05 Intel Vhost/Virtio Performance Report]
+ (//fast.dpdk.org/doc/perf/DPDK_21_05_Intel_virtio_performance_report.pdf)
+- [DPDK 21.05 Intel Crypto Performance Report]
+ (//fast.dpdk.org/doc/perf/DPDK_21_05_Intel_crypto_performance_report.pdf)
- [DPDK 21.05 Mellanox NIC Performance Report]
(//fast.dpdk.org/doc/perf/DPDK_21_05_Mellanox_NIC_performance_report.pdf)
- [DPDK 21.02 Broadcom NIC Performance Report]
(//fast.dpdk.org/doc/perf/DPDK_21_02_Broadcom_NIC_performance_report.pdf)
+- [DPDK 21.02 Intel Vhost/Virtio Performance Report]
+ (//fast.dpdk.org/doc/perf/DPDK_21_02_Intel_virtio_performance_report.pdf)
+- [DPDK 21.02 Intel Crypto Performance Report]
+ (//fast.dpdk.org/doc/perf/DPDK_21_02_Intel_crypto_performance_report.pdf)
- [DPDK 21.02 Mellanox NIC Performance Report]
(//fast.dpdk.org/doc/perf/DPDK_21_02_Mellanox_NIC_performance_report.pdf)
- [DPDK 20.11 Broadcom NIC Performance Report]
--
1.8.3.1
next reply other threads:[~2021-09-10 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 16:43 Lijuan Tu [this message]
2021-09-10 13:04 ` 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=1631292211-50614-1-git-send-email-lijuan.tu@intel.com \
--to=lijuan.tu@intel.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).