From: Stephen Hemminger <stephen@networkplumber.org>
To: Long Li <longli@microsoft.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [PATCH 2/2] eal: add meson options for hotplug MP message buffer sizes
Date: Tue, 24 Mar 2026 19:44:11 -0700 [thread overview]
Message-ID: <20260324193500.5c67857d@phoenix.local> (raw)
In-Reply-To: <20260325014506.1866374-2-longli@microsoft.com>
On Tue, 24 Mar 2026 18:45:06 -0700
Long Li <longli@microsoft.com> wrote:
> Add meson build options to allow increasing the multi-process hotplug
> message buffer limits at build time for deployments with many NICs:
> - 'dev_mp_devargs_max_len' (default 128): max device args length
> - 'mp_max_param_len' (default 256): max MP IPC message param length
>
> Example: meson setup build -Ddev_mp_devargs_max_len=256 -Dmp_max_param_len=512
>
> Guard the existing #defines with #ifndef so the meson-generated values
> from rte_build_config.h take precedence when overridden.
>
> Add a static_assert to ensure eal_dev_mp_req fits within the MP message
> param buffer, catching misconfiguration at compile time.
>
> Note: all primary and secondary processes must be built with the same
> values, as these sizes affect shared IPC message struct layouts.
>
> Signed-off-by: Long Li <longli@microsoft.com>
The whole mp API needs some work on sizing.
Ideally the message would be variable size and not include all the
file descriptors if not needed.
Even better it should be TLV encoded instead of fixed structure.
But doing this probably has to wait until 26.11.
next prev parent reply other threads:[~2026-03-25 2:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 1:45 [PATCH 1/2] eal: return error on devargs truncation in hotplug MP messages Long Li
2026-03-25 1:45 ` [PATCH 2/2] eal: add meson options for hotplug MP message buffer sizes Long Li
2026-03-25 2:44 ` Stephen Hemminger [this message]
2026-03-25 18:42 ` [EXTERNAL] " Long Li
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=20260324193500.5c67857d@phoenix.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=longli@microsoft.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