From: <lonc0002@yahoo.com>
To: <users@dpdk.org>
Subject: question about MemPool
Date: Wed, 24 Apr 2024 12:24:00 -0400 [thread overview]
Message-ID: <00d901da9663$d0f1fee0$72d5fca0$@yahoo.com> (raw)
In-Reply-To: <00d901da9663$d0f1fee0$72d5fca0$.ref@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
Hello,
When doing a rte_mempool_get_bulk() with a cache enabled mempool, first
objects are retrieved from cache and then from the common pool which I
assume is sitting in shared memory (DDR or L3?). Wouldn't accessing the
objects from the mempool in shared memory itself pull those objects into
processor cache? Can this be avoided?
Thanks,
Vince
[-- Attachment #2: Type: text/html, Size: 1873 bytes --]
next parent reply other threads:[~2024-04-24 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00d901da9663$d0f1fee0$72d5fca0$.ref@yahoo.com>
2024-04-24 16:24 ` lonc0002 [this message]
2024-04-24 16:37 ` Bing Zhao
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='00d901da9663$d0f1fee0$72d5fca0$@yahoo.com' \
--to=lonc0002@yahoo.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).