From: Stephen Hemminger <stephen@networkplumber.org>
To: "lihuisong (C)" <lihuisong@huawei.com>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>, <david.hunt@intel.com>,
<anatoly.burakov@intel.com>, <sivaprasad.tummala@amd.com>,
<liuyonglong@huawei.com>
Subject: Re: [PATCH] power: use hugepage memory for queue list entry structure
Date: Thu, 20 Feb 2025 08:11:58 -0800 [thread overview]
Message-ID: <20250220081158.345f09b0@hermes.local> (raw)
In-Reply-To: <01d163c6-6d18-03e8-ac67-e7907d27bd08@huawei.com>
On Thu, 20 Feb 2025 17:01:53 +0800
"lihuisong (C)" <lihuisong@huawei.com> wrote:
> > The queue_list_entry structure data is used in rx_callback of io path
> > when enable PMD Power Management. However its memory is currently from
> > normal heap memory. For better performance, use hugepage memory to
> > replace it.
> >
> > Signed-off-by: Huisong Li <lihuisong@huawei.com>
How is that in a hot path where this could matter?
The safety rails in rte_malloc() are much less than regular malloc().
I prefer some degree of safety from checkers and malloc library internals.
next prev parent reply other threads:[~2025-02-20 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 7:53 [PATCH] power: use hugepage memory for queue list entry structure Huisong Li
2025-02-20 9:01 ` lihuisong (C)
2025-02-20 9:41 ` Konstantin Ananyev
2025-02-24 9:23 ` lihuisong (C)
2025-02-24 11:12 ` Konstantin Ananyev
2025-02-24 12:47 ` lihuisong (C)
2025-02-20 16:11 ` Stephen Hemminger [this message]
2025-02-20 16:39 ` Konstantin Ananyev
2025-02-20 16:45 ` Stephen Hemminger
2025-02-20 16:58 ` Konstantin Ananyev
2025-02-21 11:21 ` 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=20250220081158.345f09b0@hermes.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=sivaprasad.tummala@amd.com \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.