From: Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>
To: jasvinder.singh@intel.com, bruce.richardson@intel.com,
pablo.de.lara.guarch@intel.com
Cc: dev@dpdk.org, brendan.ryan@intel.com, david.coyle@intel.com,
Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/2] net: add CRC run-time checks and AVX512/VPCLMULQDQ based CRC
Date: Tue, 29 Sep 2020 16:12:44 +0100 [thread overview]
Message-ID: <1601392366-22625-1-git-send-email-mairtin.oloingsigh@intel.com> (raw)
In-Reply-To: <1599739271-16605-1-git-send-email-mairtin.oloingsigh@intel.com>
This patchset makes two significant enhancements to the CRC modules of
the rte_net library:
1) Adds run-time selection of the optimal architecture-specific CRC path.
Previously the selection was solely made at compile-time, meaning it
could only be built and run on the same generation of CPU. Adding
run-time selection ability means this can be used from distro packages
and/or DPDK can be compiled on an older CPU and run on a newer CPU.
2) Adds an optimized CRC implementation based on the AVX512 and
VPCLMULQDQ instruction sets.
For further details, please see the commit messages of the individual
patches.
v2:
* Added support for run-time selection of optimal architecture-specific
CRC, based on v1 review comment.
* Added full working AVX512/VPCLMULDQD support for CRC32-Ethernet and
CRC16-CCITT.
v1:
* Initial version, with incomplete AVX512/VPCLMULDQD support for
CRC32-Ethernet only.
Mairtin o Loingsigh (2):
net: add run-time architecture specific CRC selection
net: add support for AVX512/VPCLMULQDQ based CRC
app/test/test_crc.c | 11 +-
config/x86/meson.build | 6 +-
doc/guides/rel_notes/release_20_11.rst | 6 +
lib/librte_net/meson.build | 89 ++++-
lib/librte_net/net_crc.h | 45 +++
lib/librte_net/net_crc_avx512.c | 424 ++++++++++++++++++++++
lib/librte_net/{net_crc_neon.h => net_crc_neon.c} | 27 +-
lib/librte_net/{net_crc_sse.h => net_crc_sse.c} | 34 +-
lib/librte_net/rte_net_crc.c | 100 +++--
lib/librte_net/rte_net_crc.h | 4 +-
10 files changed, 674 insertions(+), 72 deletions(-)
create mode 100644 lib/librte_net/net_crc.h
create mode 100644 lib/librte_net/net_crc_avx512.c
rename lib/librte_net/{net_crc_neon.h => net_crc_neon.c} (95%)
rename lib/librte_net/{net_crc_sse.h => net_crc_sse.c} (94%)
--
2.12.3
next prev parent reply other threads:[~2020-09-29 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 12:01 [dpdk-dev] [PATCH] net: add support for AVX512 when generating CRC Mairtin o Loingsigh
2020-09-10 12:27 ` Bruce Richardson
2020-09-10 12:52 ` O'loingsigh, Mairtin
2020-09-29 15:45 ` O'loingsigh, Mairtin
2020-09-11 9:57 ` De Lara Guarch, Pablo
2020-09-29 15:47 ` O'loingsigh, Mairtin
2020-09-29 15:12 ` Mairtin o Loingsigh [this message]
2020-09-29 15:41 ` [dpdk-dev] [PATCH v2 0/2] net: add CRC run-time checks and AVX512/VPCLMULQDQ based CRC O'loingsigh, Mairtin
2020-09-29 15:12 ` [dpdk-dev] [PATCH v2 1/2] net: add run-time architecture specific CRC selection Mairtin o Loingsigh
2020-09-29 15:12 ` [dpdk-dev] [PATCH v2 2/2] net: add support for AVX512/VPCLMULQDQ based CRC Mairtin o Loingsigh
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=1601392366-22625-1-git-send-email-mairtin.oloingsigh@intel.com \
--to=mairtin.oloingsigh@intel.com \
--cc=brendan.ryan@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.coyle@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=pablo.de.lara.guarch@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).