From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id A6DD842542;
	Fri,  8 Sep 2023 09:28:13 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 52F2D40274;
	Fri,  8 Sep 2023 09:28:13 +0200 (CEST)
Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3])
 by mails.dpdk.org (Postfix) with ESMTP id AA76A40042
 for <dev@dpdk.org>; Fri,  8 Sep 2023 09:28:12 +0200 (CEST)
Received: from mail.lysator.liu.se (localhost [127.0.0.1])
 by mail.lysator.liu.se (Postfix) with ESMTP id 4F58E1CF6A
 for <dev@dpdk.org>; Fri,  8 Sep 2023 09:28:12 +0200 (CEST)
Received: by mail.lysator.liu.se (Postfix, from userid 1004)
 id 4E16A1CF69; Fri,  8 Sep 2023 09:28:12 +0200 (CEST)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 hermod.lysator.liu.se
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=ALL_TRUSTED, AWL, NICE_REPLY_A
 autolearn=disabled version=3.4.6
X-Spam-Score: -2.3
Received: from [192.168.1.59] (h-62-63-215-114.A163.priv.bahnhof.se
 [62.63.215.114])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by mail.lysator.liu.se (Postfix) with ESMTPSA id C3C791D2AD;
 Fri,  8 Sep 2023 09:28:11 +0200 (CEST)
Message-ID: <7d0f8f9b-d3a2-d6fb-adad-4be48ff02449@lysator.liu.se>
Date: Fri, 8 Sep 2023 09:28:11 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.15.0
Subject: Re: quick thread in DLB2
Content-Language: en-US
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>
References: <2363761.yKrmzQ4Hd0@thomas> <20230906124526.02c5fe61@hermes.local>
 <BYAPR11MB31582C7727272F6F7E9517F3E9EEA@BYAPR11MB3158.namprd11.prod.outlook.com>
From: =?UTF-8?Q?Mattias_R=c3=b6nnblom?= <hofors@lysator.liu.se>
In-Reply-To: <BYAPR11MB31582C7727272F6F7E9517F3E9EEA@BYAPR11MB3158.namprd11.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

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.