From: MOD <sdk.register@gmail.com>
To: users@dpdk.org
Subject: Configuring memory segments values
Date: Tue, 2 Aug 2022 10:33:56 +0300 [thread overview]
Message-ID: <CA+Md9nyqHUizqFRuYSOOqKo2ZpNcWR4N+kgP1z+VqU_PvYpLqQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
Hi All,
First of all, I am using DPDK 20.11, and RHEL7.2
I have encountered the `couldnt find suitable memseg_list` error in my
program
From what I could gather I should be able to solve this issue by modifying
the following values in rte_config.h:
#define RTE_MAX_HEAPS 32
#define RTE_MAX_MEMSEG_LISTS 128
#define RTE_MAX_MEMSEG_PER_LIST 8192
#define RTE_MAX_MEM_MB_PER_LIST 32768
#define RTE_MAX_MEMSEG_PER_TYPE 32768
#define RTE_MAX_MEM_MB_PER_TYPE 65536
#define RTE_MAX_MEMZONE 2560 My questions are:
1. can I get information about memseg usage in runtime?
2. given my architecture (x86), RAM capacity (200G of 1GB hugepages), NUMA
setup (2 NUMAs), how do I calculate appropriate values?
[-- Attachment #2: Type: text/html, Size: 7133 bytes --]
reply other threads:[~2022-08-02 7:34 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+Md9nyqHUizqFRuYSOOqKo2ZpNcWR4N+kgP1z+VqU_PvYpLqQ@mail.gmail.com \
--to=sdk.register@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).