From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Jake Freeland <jfree@FreeBSD.org>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v2 2/3] eal/freebsd: Avoid claiming memseg holes
Date: Mon, 13 Oct 2025 15:12:44 +0200 [thread overview]
Message-ID: <ee355946-16f7-4876-bc05-65b4de5b8185@intel.com> (raw)
In-Reply-To: <20250814213246.4141803-3-jfree@FreeBSD.org>
On 8/14/2025 11:32 PM, Jake Freeland wrote:
> When need_hole is false, memseg searches will only be done for a single
> element. If the search starts at beginning of the list, an element that
> was previously reserved as a hole may be wrongly claimed.
>
> To avoid this, begin the search following the last used entry. This way,
> we ignore all pre-existing holes.
>
> Signed-off-by: Jake Freeland <jfree@FreeBSD.org>
> ---
> lib/eal/freebsd/eal_memory.c | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/lib/eal/freebsd/eal_memory.c b/lib/eal/freebsd/eal_memory.c
> index be3bde2cb9..b159e9ef4e 100644
> --- a/lib/eal/freebsd/eal_memory.c
> +++ b/lib/eal/freebsd/eal_memory.c
> @@ -143,6 +143,7 @@ rte_eal_hugepage_init(void)
>
> for (msl_idx = 0; msl_idx < RTE_MAX_MEMSEG_LISTS;
> msl_idx++) {
> + int start_idx, num_elems;
> bool empty, need_hole;
> msl = &mcfg->memsegs[msl_idx];
> arr = &msl->memseg_arr;
> @@ -157,10 +158,24 @@ rte_eal_hugepage_init(void)
> * adjacent to current one.
> */
> need_hole = !empty && !is_adjacent;
> + if (need_hole) {
> + start_idx = 0;
> + /* we need 1, plus hole */
> + num_elems = 2;
> + } else {
> + /* begin our search after the last used
> + * element in the list, skipping over
> + * any previously placed holes
> + */
> + start_idx = rte_fbarray_find_prev_n_used(
> + arr, arr->len - 1, 1) + 1;
> + if (start_idx < 0)
> + start_idx = 0;
Actually, I think this check is largely redundant, because even if
find_prev_n_used returns -1 (empty array case), we immediately +1 the
result, so it's always 0 at a minimum.
> + num_elems = 1;
> + }
>
> - /* we need 1, plus hole if not adjacent */
> ms_idx = rte_fbarray_find_next_n_free(arr,
> - 0, 1 + (need_hole ? 1 : 0));
> + start_idx, num_elems);
>
> /* memseg list is full? */
> if (ms_idx < 0)
--
Thanks,
Anatoly
next prev parent reply other threads:[~2025-10-13 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 21:32 [PATCH v2 0/3] EAL memory fixes Jake Freeland
2025-08-14 21:32 ` [PATCH v2 1/3] eal/freebsd: Do not use prev_ms_idx for hole detection Jake Freeland
2025-10-13 12:23 ` Burakov, Anatoly
2025-08-14 21:32 ` [PATCH v2 2/3] eal/freebsd: Avoid claiming memseg holes Jake Freeland
2025-10-13 12:36 ` Burakov, Anatoly
2025-10-13 13:12 ` Burakov, Anatoly [this message]
2025-08-14 21:32 ` [PATCH v2 3/3] eal/linux: Check hugepage access permissions Jake Freeland
2025-10-13 12:43 ` Burakov, Anatoly
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=ee355946-16f7-4876-bc05-65b4de5b8185@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jfree@FreeBSD.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).