From: fengchengwen <fengchengwen@huawei.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>, <dev@dpdk.org>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Pallavi Kadam <pallavi.kadam@intel.com>
Subject: Re: [RFC PATCH v1 5/5] lcore: store physical package ID internally
Date: Mon, 9 Sep 2024 15:49:28 +0800 [thread overview]
Message-ID: <2fd7a64f-7cb2-0057-2d4b-2a8ffe9e4ffb@huawei.com> (raw)
In-Reply-To: <f68d303116b86fd1df004c43941c72444a697c9d.1725622420.git.anatoly.burakov@intel.com>
It seemed there is no usage scenario of the new field, suggest add it when we indeed need it.
On 2024/9/6 19:47, Anatoly Burakov wrote:
> This patch introduces a new field in the lcore structure that stores the
> physical package ID of the core. This field is populated during EAL init.
> It is not exposed through any external API's for now.
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
...
next prev parent reply other threads:[~2024-09-09 7:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 11:47 [RFC PATCH v1 0/5] Adjust wording for NUMA vs. socket ID in DPDK Anatoly Burakov
2024-09-06 11:47 ` [RFC PATCH v1 1/5] eal: update socket ID API documentation Anatoly Burakov
2024-09-06 11:47 ` [RFC PATCH v1 2/5] lcore: rename socket ID to NUMA ID Anatoly Burakov
2024-09-06 11:47 ` [RFC PATCH v1 3/5] eal: rename socket ID to NUMA ID in internal config Anatoly Burakov
2024-09-06 11:47 ` [RFC PATCH v1 4/5] eal: rename --socket-mem/--socket-limit Anatoly Burakov
2024-09-09 7:42 ` fengchengwen
2024-09-06 11:47 ` [RFC PATCH v1 5/5] lcore: store physical package ID internally Anatoly Burakov
2024-09-09 7:49 ` fengchengwen [this message]
2024-09-06 12:37 ` [RFC PATCH v1 0/5] Adjust wording for NUMA vs. socket ID in DPDK Morten Brørup
2024-09-06 12:46 ` Burakov, Anatoly
2024-09-06 13:02 ` Morten Brørup
2024-09-06 13:07 ` Bruce Richardson
2024-09-06 13:17 ` Burakov, Anatoly
2024-09-06 13:58 ` Morten Brørup
2024-09-09 7:51 ` fengchengwen
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=2fd7a64f-7cb2-0057-2d4b-2a8ffe9e4ffb@huawei.com \
--to=fengchengwen@huawei.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=pallavi.kadam@intel.com \
--cc=roretzla@linux.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;
as well as URLs for NNTP newsgroup(s).