DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: anatoly.burakov@intel.com
Cc: david.marchand@redhat.com, bruce.richardson@intel.com,
	dev@dpdk.org, Kefu Chai <tchaikov@gmail.com>,
	avi@scylladb.com
Subject: configuration of memseg lists number
Date: Thu, 02 Nov 2023 11:04:24 +0100	[thread overview]
Message-ID: <3585796.R56niFO833@thomas> (raw)

Hello,

While looking at Seastar, I see it uses this patch on top of DPDK:

	build: add meson options of max_memseg_lists

	RTE_MAX_MEMSEG_LISTS = 128 is not enough for high-memory machines,
	in our case, we need to increase it to 8192.
	so add an option so user can override it.

	https://github.com/scylladb/dpdk/commit/cafaa3cf457584de

I think we could allow to configure this at runtime,
as we did already for RTE_MAX_MEMZONE:
we've added rte_memzone_max_set() / rte_memzone_max_get().

Opinions, comments, volunteers?



             reply	other threads:[~2023-11-02 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 10:04 Thomas Monjalon [this message]
2023-11-05  9:56 ` Avi Kivity
2023-11-06  4:35   ` kefu chai

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=3585796.R56niFO833@thomas \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=avi@scylladb.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=tchaikov@gmail.com \
    /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).