From: "Jianyue Wu" <wujianyue000@163.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: "Tyler Retzlaff" <roretzla@linux.microsoft.com>,
ferruh.yigit@amd.com, "dev@dpdk.org" <dev@dpdk.org>,
"jianyue.wu@nokia-sbell.com" <jianyue.wu@nokia-sbell.com>
Subject: Re:Re: [PATCH v2] eal/linux: enhanced error handling for affinity
Date: Sun, 28 Apr 2024 20:26:18 +0800 (CST) [thread overview]
Message-ID: <5afd96e5.d333.18f24ab9f10.Coremail.wujianyue000@163.com> (raw)
In-Reply-To: <20240426171853.7649b935@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
Yes, agree with that, there is also trace from kernel can see that. I'll ignore this patch.
At 2024-04-27 08:18:53, "Stephen Hemminger" <stephen@networkplumber.org> wrote:
>On Fri, 26 Apr 2024 08:47:37 -0700
>Tyler Retzlaff <roretzla@linux.microsoft.com> wrote:
>
>> > int
>> > --
>>
>> i do not think introducing os specific behavior/logging to the EAL
>> is a good idea. logging although not formally part of the api surface
>> should present the same experience for all platforms. the EAL should
>> have a higher standard here.
>>
>> > 2.34.1
>
>For this case, the error message would be better if there was some way
>to look at the cgroups and mark the cores that are not available as if
>they were offline lcores.
>
>
[-- Attachment #2: Type: text/html, Size: 988 bytes --]
prev parent reply other threads:[~2024-04-29 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 11:11 Jianyue Wu
2024-04-26 15:47 ` Tyler Retzlaff
2024-04-27 0:18 ` Stephen Hemminger
2024-04-28 12:26 ` Jianyue Wu [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=5afd96e5.d333.18f24ab9f10.Coremail.wujianyue000@163.com \
--to=wujianyue000@163.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jianyue.wu@nokia-sbell.com \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.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).