DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jiang Aengus <aengusjiang@hotmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: rte_hash socket memory usage is not balance issue
Date: Mon, 16 Dec 2024 07:40:58 +0000	[thread overview]
Message-ID: <ME0P300MB103892238F653BC48B60E1F2AF3B2@ME0P300MB1038.AUSP300.PROD.OUTLOOK.COM> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 439 bytes --]

steps:
1.master thread create rte_hash for every socket with same size. each socket hash with the each socket_id pass by rte_hash_param.socket_id
2.use numasta -p `pidof your_app` like below:
[cid:a0ba8efb-58a9-4cca-b773-724878024a3e]

review the sourcec code dpdk23.11 found that:
it will allocate memory with the rte_zmalloc api, this api is use socket of current lcore, not use the args rte_hash_param socket_id field value.



[-- Attachment #1.2: Type: text/html, Size: 976 bytes --]

[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 17631 bytes --]

                 reply	other threads:[~2024-12-17  8:02 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=ME0P300MB103892238F653BC48B60E1F2AF3B2@ME0P300MB1038.AUSP300.PROD.OUTLOOK.COM \
    --to=aengusjiang@hotmail.com \
    --cc=dev@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).