From: fwefew 4t4tg <7532yahoo@gmail.com>
To: users@dpdk.org
Subject: Follow-up to cache misses allocating mbufs
Date: Sat, 22 Jun 2024 21:16:33 -0400 [thread overview]
Message-ID: <CA+Tq66We8oaWwqF9k9uVnJ2o8qgt2f5H3fVzYvmYnqDX+yq6Og@mail.gmail.com> (raw)
Well, after playing with a little more I learned two things:
- bulk get/put is much faster and LLC friendly
- warming up the cache helps
See https://pastebin.com/m7QVjUdk for data.
reply other threads:[~2024-06-23 1:17 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=CA+Tq66We8oaWwqF9k9uVnJ2o8qgt2f5H3fVzYvmYnqDX+yq6Og@mail.gmail.com \
--to=7532yahoo@gmail.com \
--cc=users@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).