From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Kaisen You <kaisenx.you@intel.com>, <dev@dpdk.org>
Cc: <yidingx.zhou@intel.com>, <thomas@monjalon.net>,
<david.marchand@redhat.com>, <olivier.matz@6wind.com>,
<ferruh.yigit@amd.com>, <zhoumin@loongson.cn>, <stable@dpdk.org>
Subject: Re: [PATCH v5] enhance NUMA affinity heuristic
Date: Wed, 15 Feb 2023 14:47:33 +0000 [thread overview]
Message-ID: <8144d710-2201-e10b-5a42-9fddd8cafa1e@intel.com> (raw)
In-Reply-To: <6014e44e-5dd5-365f-2a8f-0ec37f562ca8@intel.com>
On 2/15/2023 2:22 PM, Burakov, Anatoly wrote:
> On 2/1/2023 12:20 PM, Kaisen You wrote:
>> Trying to allocate memory on the first detected numa node has less
>> chance to find some memory actually available rather than on the main
>> lcore numa node (especially when the DPDK application is started only
>> on one numa node).
>>
>> Fixes: 705356f0811f ("eal: simplify control thread creation")
>> Fixes: bb0bd346d5c1 ("eal: suggest using --lcores option")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: David Marchand <david.marchand@redhat.com>
>> Signed-off-by: Kaisen You <kaisenx.you@intel.com>
>> ---
>> Changes since v4:
>> - mod the patch title,
>>
>> Changes since v3:
>> - add the assignment of socket_id in thread initialization,
>>
>> Changes since v2:
>> - add uncommitted local change and fix compilation,
>>
>> Changes since v1:
>> - accomodate for configurations with main lcore running on multiples
>> physical cores belonging to different numa,
>> ---
>> lib/eal/common/eal_common_thread.c | 1 +
>> lib/eal/common/malloc_heap.c | 4 ++++
>> 2 files changed, 5 insertions(+)
>>
>> diff --git a/lib/eal/common/eal_common_thread.c
>> b/lib/eal/common/eal_common_thread.c
>> index 38d83a6885..21bff971f8 100644
>> --- a/lib/eal/common/eal_common_thread.c
>> +++ b/lib/eal/common/eal_common_thread.c
>> @@ -251,6 +251,7 @@ static void *ctrl_thread_init(void *arg)
>> void *routine_arg = params->arg;
>> __rte_thread_init(rte_lcore_id(), cpuset);
>> + RTE_PER_LCORE(_socket_id) = SOCKET_ID_ANY;
>> params->ret = rte_thread_set_affinity_by_id(rte_thread_self(),
>> cpuset);
>> if (params->ret != 0) {
>> __atomic_store_n(¶ms->ctrl_thread_status,
>> diff --git a/lib/eal/common/malloc_heap.c b/lib/eal/common/malloc_heap.c
>> index d7c410b786..3ee19aee15 100644
>> --- a/lib/eal/common/malloc_heap.c
>> +++ b/lib/eal/common/malloc_heap.c
>> @@ -717,6 +717,10 @@ malloc_get_numa_socket(void)
>> return socket_id;
>> }
>> + socket_id = rte_lcore_to_socket_id(rte_get_main_lcore());
>> + if (socket_id != (unsigned int)SOCKET_ID_ANY)
>> + return socket_id;
>> +
>> return rte_socket_id_by_idx(0);
>> }
>
> I may be lacking context, but I don't quite get the suggested change.
> From what I understand, the original has to do with assigning lcore
> cpusets in such a way that an lcore ends up having two socket ID's
> (because it's been assigned to CPU's on different sockets). Why is this
> allowed in the first place? It seems like a user error to me, as it
> breaks many of the fundamental assumptions DPDK makes.
>
> I'm fine with using main lcore socket for control threads, I just don't
> think the `socket_id != SOCKET_ID_ANY` thing should be checked here,
> because it apparently tries to compensate for a problem with cpuset of
> the main thread, which shouldn't have happened to begin with.
>
Just to be clear: I don't have any objections to this patch otherwise.
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2023-02-15 14:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221221104858.296530-1-david.marchand@redhat.com>
2023-01-31 15:05 ` [PATCH v4] net/iavf:enhance " Kaisen You
2023-01-31 16:05 ` Thomas Monjalon
2023-02-01 5:32 ` You, KaisenX
2023-02-01 12:20 ` [PATCH v5] enhance " Kaisen You
2023-02-15 14:22 ` Burakov, Anatoly
2023-02-15 14:47 ` Burakov, Anatoly [this message]
2023-02-16 2:50 ` You, KaisenX
2023-03-03 14:07 ` Thomas Monjalon
2023-03-09 1:58 ` You, KaisenX
2023-04-13 0:56 ` You, KaisenX
2023-04-19 12:16 ` Thomas Monjalon
2023-04-21 2:34 ` You, KaisenX
2023-04-21 8:12 ` Thomas Monjalon
2023-04-23 6:52 ` You, KaisenX
2023-04-23 8:57 ` You, KaisenX
2023-04-23 13:19 ` Thomas Monjalon
2023-04-25 5:16 ` [PATCH v6] " Kaisen You
2023-04-27 6:57 ` Thomas Monjalon
2023-05-16 5:19 ` You, KaisenX
2023-05-23 2:50 ` [PATCH v7] " Kaisen You
2023-05-23 10:44 ` Burakov, Anatoly
2023-05-26 6:44 ` You, KaisenX
2023-05-23 12:45 ` Burakov, Anatoly
2023-05-26 6:50 ` [PATCH v8] " Kaisen You
2023-05-26 8:45 ` Kaisen You
2023-05-26 14:44 ` Burakov, Anatoly
2023-05-26 17:50 ` Stephen Hemminger
2023-05-29 10:37 ` Burakov, Anatoly
2023-06-01 14:42 ` David Marchand
2023-06-06 14:04 ` Thomas Monjalon
2023-06-12 9:36 ` 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=8144d710-2201-e10b-5a42-9fddd8cafa1e@intel.com \
--to=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=kaisenx.you@intel.com \
--cc=olivier.matz@6wind.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yidingx.zhou@intel.com \
--cc=zhoumin@loongson.cn \
/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).