From: "Morten Brørup" <mb@smartsharesystems.com>
To: <dev@dpdk.org>, "Thomas Monjalon" <thomas@monjalon.net>
Subject: SmartShare Systems DPDK v22.11 roadmap
Date: Sat, 3 Sep 2022 13:09:34 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D872F0@smartserver.smartshare.dk> (raw)
SmartShare Systems DPDK v22.11 roadmap
======================================
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 RFC and discussion:
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-09-03 11:09 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=98CBD80474FA8B44BF855DF32C47DC35D872F0@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).