From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Fidaullah Noonari <fidaullah.noonari@emumba.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] eal: change alloc_sz calculation which may cause unnecessarily allocation
Date: Wed, 27 Jul 2022 11:23:39 +0300 [thread overview]
Message-ID: <20220727112339.3bc5e9b1@sovereign> (raw)
In-Reply-To: <20220718041142.411770-1-fidaullah.noonari@emumba.com>
2022-07-18 09:11 (UTC+0500), Fidaullah Noonari:
> In try_expand_heap() alloc_sz is calculated
> which may result in unnecessary allocation of whole huge page,
> this may cause allocation limit from system or eal
Let me suggest a rewording:
The amount of memory to allocate from the system for heap expansion
was calculated in a way that may yield one page more than needed.
This could hit the allocation limit from the system or EAL.
The allocation would fail despite enough memory being available.
> In response to this mail:
> <CAEYuUWCnRZNwxiOHEeTHw0Gy9aFJRLZtvAG9g=smuUvUEMcFXg@mail.gmail.com>
Proper links to mails.dpdk.org or inbox.dpdk.org are preferred.
>
> Signed-off-by: Fidaullah Noonari <fidaullah.noonari@emumba.com>
> ---
> lib/eal/common/malloc_heap.c | 2 +-
> lib/eal/common/malloc_mp.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/eal/common/malloc_heap.c b/lib/eal/common/malloc_heap.c
> index 27a52266ad..e348e385e4 100644
> --- a/lib/eal/common/malloc_heap.c
> +++ b/lib/eal/common/malloc_heap.c
> @@ -402,7 +402,7 @@ try_expand_heap_primary(struct malloc_heap *heap, uint64_t pg_sz,
> int n_segs;
> bool callback_triggered = false;
>
> - alloc_sz = RTE_ALIGN_CEIL(align + elt_size +
> + alloc_sz = RTE_ALIGN_CEIL(RTE_ALIGN_CEIL(align, elt_size) +
> MALLOC_ELEM_OVERHEAD, pg_sz);
> n_segs = alloc_sz / pg_sz;
>
> diff --git a/lib/eal/common/malloc_mp.c b/lib/eal/common/malloc_mp.c
> index 2b8eb51067..1b79ed5e21 100644
> --- a/lib/eal/common/malloc_mp.c
> +++ b/lib/eal/common/malloc_mp.c
> @@ -249,7 +249,7 @@ handle_alloc_request(const struct malloc_mp_req *m,
> return -1;
> }
>
> - alloc_sz = RTE_ALIGN_CEIL(ar->align + ar->elt_size +
> + alloc_sz = RTE_ALIGN_CEIL(RTE_ALIGN_CEIL(ar->align, ar->elt_size) +
> MALLOC_ELEM_OVERHEAD, ar->page_sz);
> n_segs = alloc_sz / ar->page_sz;
>
Wrong argument order for RTE_ALIGN_CEIL(size, alignment) in both places.
prev parent reply other threads:[~2022-07-27 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 4:11 Fidaullah Noonari
2022-07-27 8:23 ` Dmitry Kozlyuk [this message]
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=20220727112339.3bc5e9b1@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=fidaullah.noonari@emumba.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).