From: Bing Zhao <bingz@nvidia.com>
To: "lonc0002@yahoo.com" <lonc0002@yahoo.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: RE: question about MemPool
Date: Wed, 24 Apr 2024 16:37:15 +0000 [thread overview]
Message-ID: <DM4PR12MB5184D25E5E09902B59B4EE04D0102@DM4PR12MB5184.namprd12.prod.outlook.com> (raw)
In-Reply-To: <00d901da9663$d0f1fee0$72d5fca0$@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
The concept of memory pool cache is different from the CPU architecture cache.
Unlike some DSP, in the modern CPU and system, it is not a common use case to assign addresses to the cache and lock them as a memory. In especial, the data buffer is too large.
The memory pool cache is a LIFO to store the pointers and trying to reduce the memory footprints and reduce the CPU cache conflict and eviction. (Always try to use the used memory previously)
Only when trying to access the memory itself, a whole cache line will be checked and try to be loaded. It is impossible that a CPU load a whole buffer (2KB for example) directly without any READ / WRITE / FLUSH to the cache.
BR. Bing
From: lonc0002@yahoo.com <lonc0002@yahoo.com>
Sent: Thursday, April 25, 2024 12:24 AM
To: users@dpdk.org
Subject: question about MemPool
External email: Use caution opening links or attachments
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: 5674 bytes --]
prev parent reply other threads:[~2024-04-24 16:37 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
2024-04-24 16:37 ` Bing Zhao [this message]
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=DM4PR12MB5184D25E5E09902B59B4EE04D0102@DM4PR12MB5184.namprd12.prod.outlook.com \
--to=bingz@nvidia.com \
--cc=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).