From: "Morten Brørup" <mb@smartsharesystems.com>
To: <dev@dpdk.org>
Subject: SmartShare Systems DPDK 23.03 roadmap
Date: Thu, 1 Dec 2022 17:20:46 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D8753D@smartserver.smartshare.dk> (raw)
mempool cache zero-copy get/put bulk
------------------------------------
Zero-copy access to mempool caches is beneficial for PMD performance, and
must be provided by the mempool library to fix [Bug 1052] without a
performance regression.
[Bug 1052]: https://bugs.dpdk.org/show_bug.cgi?id=1052
Refer to patch v2 and RFC discussions:
http://inbox.dpdk.org/dev/20221116180419.98937-1-mb@smartsharesystems.com/
http://inbox.dpdk.org/dev/98CBD80474FA8B44BF855DF32C47DC35D87489@smartserver.smartshare.dk/
Non-temporal memory copy
------------------------
The primary purpose of this feature is to avoid polluting the CPU's data
cache when copying packets using the CPU, e.g. when capturing packets.
E.g. copying a 32 packet burst of 1514 B packets reads 48 KB and writes
48 KB, and thus pollutes the entire L1 cache of a typical x86 CPU core
with 64 KB data cache.
The API for this feature is generic, but we will initially only implement
the feature for x86 architecture. This implementation can be used as
inspiration for implementations for other architectures.
Refer to patch v4 and RFC discussions:
http://inbox.dpdk.org/dev/20221010064600.16495-1-mb@smartsharesystems.com/
http://inbox.dpdk.org/dev/98CBD80474FA8B44BF855DF32C47DC35D871D4@smartserver.smartshare.dk/
http://inbox.dpdk.org/dev/98CBD80474FA8B44BF855DF32C47DC35D8728A@smartserver.smartshare.dk/
Med venlig hilsen / Kind regards,
-Morten Brørup
reply other threads:[~2022-12-01 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=98CBD80474FA8B44BF855DF32C47DC35D8753D@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@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).