DPDK usage discussions
 help / color / mirror / Atom feed
From: MOD <sdk.register@gmail.com>
To: users@dpdk.org
Subject: Difficulty with legacy mem mode DPDK 20.11
Date: Sun, 7 Nov 2021 16:04:11 +0200
Message-ID: <CA+Md9nyQ8KH1_zpLN8_cWdCHfgeE1=z8vHPOYZxWbZH_W6GCMw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

hi,
we are in the process of upgrading to DPDK 20.11 from DPDK 17.11. We have
encountered an issue where the secondary process fails to allocate it's
needed memory, and have decided to use the --legacy-mem option for an
easier upgrade (If there's a way to make the dynamic allocation work, we
would like to hear about it as well).
when starting up the application with legacy-mem, it starts to allocate
resources, and then this error occurs (We are trying to allocate 256GB of
1-GB hugepages):

 Could not find space for memseg. Please increase 32768 and/or 65536
in configuration.

This error is referring (according to the source code) to the
RTE_MAX_MEMSEG_PER_TYPE and RTE_MAX_MEM_MB_PER_TYPE variables at
rte_config.h
We tried doing some research about  them, and came up with the following:

A type is page size + NUMA combination (for example, 2 NUMAs and only 2MB
pages are 2 types)

RTE_MAX_MEMSEG_LISTS: A memseg is a memory page, and at list one list
should exists per type
RTE_MAX_MEMSEG_PER_LIST and RTE_MAX_MEM_MB_PER_LIST are self explanatory
RTE_MAX_MEMSEG_PER_TYPE and RTE_MAX_MEM_MB_PER_TYPE are also self
explanatory

changing the values according to our desired settings doesn't seem to solve
the problem, so are we missing something?

Thanks in advance!

[-- Attachment #2: Type: text/html, Size: 2310 bytes --]

                 reply	other threads:[~2021-11-07 14:04 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+Md9nyQ8KH1_zpLN8_cWdCHfgeE1=z8vHPOYZxWbZH_W6GCMw@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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git