From: "Morten Brørup" <mb@smartsharesystems.com>
To: <dev@dpdk.org>
Cc: "Bruce Richardson" <bruce.richardson@intel.com>,
"Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>,
"Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Mattias Rönnblom" <hofors@lysator.liu.se>
Subject: RE: [RFC v3] non-temporal memcpy
Date: Wed, 7 Sep 2022 11:22:15 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D872FF@smartserver.smartshare.dk> (raw)
> From: Morten Brørup
> Sent: Friday, 19 August 2022 15.58
>
> This RFC proposes a set of functions optimized for non-temporal memory
> copy.
>
> At this stage, I am asking for acceptance of the concept and API.
> Feedback on the x86 implementation is also welcome.
Potential reviewers: An updated version will follow. Please don't review this version.
-Morten
next reply other threads:[~2022-09-07 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 9:22 Morten Brørup [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-19 13:58 Morten Brørup
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=98CBD80474FA8B44BF855DF32C47DC35D872FF@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hofors@lysator.liu.se \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=stephen@networkplumber.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).