From: "Mattias Rönnblom" <hofors@lysator.liu.se>
To: "Sevincer, Abdullah" <abdullah.sevincer@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: quick thread in DLB2
Date: Wed, 13 Sep 2023 17:48:09 +0200 [thread overview]
Message-ID: <b0ea9a28-4378-35e6-6730-a0406e2e4899@lysator.liu.se> (raw)
In-Reply-To: <BYAPR11MB3158CB5459CDDDB38F58A08AE9F2A@BYAPR11MB3158.namprd11.prod.outlook.com>
On 2023-09-11 16:28, Sevincer, Abdullah wrote:
> Mattias,
> Yes that’s correct.
>
>
There is no way to cleaner and more robust way to achieve the same
result? For example, by accessing /proc, or better, an DPDK abstraction
of the same.
> -----Original Message-----
> From: Mattias Rönnblom <hofors@lysator.liu.se>
> Sent: Friday, September 8, 2023 12:28 AM
> To: Sevincer, Abdullah <abdullah.sevincer@intel.com>; Stephen Hemminger <stephen@networkplumber.org>; Thomas Monjalon <thomas@monjalon.net>
> Cc: dev@dpdk.org; Tyler Retzlaff <roretzla@linux.microsoft.com>
> Subject: Re: quick thread in DLB2
>
> On 2023-09-08 00:09, Sevincer, Abdullah wrote:
>> Hi Stephen,
>> It is probing ports for best CPU. Yes it collects cycles. We may rework in the future.
>
> Best, in what sense? Is this some kind of topology exploration? One DLB port being closer to (cheaper to access for) certain cores?
>
>> Open to suggestions.
>>
>> -----Original Message-----
>> From: Stephen Hemminger <stephen@networkplumber.org>
>> Sent: Wednesday, September 6, 2023 12:45 PM
>> To: Thomas Monjalon <thomas@monjalon.net>
>> Cc: Sevincer, Abdullah <abdullah.sevincer@intel.com>; dev@dpdk.org;
>> Tyler Retzlaff <roretzla@linux.microsoft.com>
>> Subject: Re: quick thread in DLB2
>>
>> On Fri, 01 Sep 2023 16:08:48 +0200
>> Thomas Monjalon <thomas@monjalon.net> wrote:
>>
>>> Hello Abdullah,
>>>
>>> In the DLB2 code, I see a thread is created for a single operation:
>>> In drivers/event/dlb2/pf/base/dlb2_resource.c
>>> pthread_create(&pthread, NULL, &dlb2_pp_profile_func,
>>> &dlb2_thread_data[i]); and just after:
>>> pthread_join(pthread, NULL);
>>>
>>> Can we avoid creating this thread?
>>> I guess no, because it must spawn on a specific CPU.
>>>
>>>
>>
>> The per thread data seems to break lots of expectations in EAL.
>> It all seems to be about capturing the number of cycles on different cores.
>> Looks like a mess.
next prev parent reply other threads:[~2023-09-13 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 14:08 Thomas Monjalon
2023-09-04 19:13 ` Sevincer, Abdullah
2023-09-06 19:45 ` Stephen Hemminger
2023-09-07 22:09 ` Sevincer, Abdullah
2023-09-07 23:37 ` Stephen Hemminger
2023-09-08 7:28 ` Mattias Rönnblom
2023-09-11 14:28 ` Sevincer, Abdullah
2023-09-13 15:48 ` Mattias Rönnblom [this message]
2023-09-13 20:56 ` Honnappa Nagarahalli
2023-09-14 8:09 ` Mattias Rönnblom
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=b0ea9a28-4378-35e6-6730-a0406e2e4899@lysator.liu.se \
--to=hofors@lysator.liu.se \
--cc=abdullah.sevincer@intel.com \
--cc=dev@dpdk.org \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.org \
--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 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).