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 327C4A050B;
	Thu,  7 Apr 2022 00:03:26 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id C737F40689;
	Thu,  7 Apr 2022 00:03:25 +0200 (CEST)
Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com
 [209.85.208.172])
 by mails.dpdk.org (Postfix) with ESMTP id B21154014F
 for <dev@dpdk.org>; Thu,  7 Apr 2022 00:03:23 +0200 (CEST)
Received: by mail-lj1-f172.google.com with SMTP id q14so5042820ljc.12
 for <dev@dpdk.org>; Wed, 06 Apr 2022 15:03:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=date:from:to:cc:subject:message-id:in-reply-to:references
 :mime-version:content-transfer-encoding;
 bh=OYTrh5g5Dg1lHjwbtOGL94Ip4WGe9pRX4Okm0mk4hyI=;
 b=HQQZ5/Ijkj0i6A/aGzBcs7srAYXUObyAuVqOV8a6aXnfUvN56Mxq0+owH2ISHKfklz
 ZdMZ37F4ee31Ts8D1nu8bZLMh8HwFFsrBKr2aAVhy/3icCZDQCrDyISvHaXGt1nPWbZ3
 pQiytLqWGQKeb+JHjZ1JvUETDnBl4pP+OhSpbVFYcDbVDAWG+R/8J6j+RJG0aIpopDgr
 GRrp6Z4jTNP0USaqvVUJsae2RFiftNB5pdTMC4Ah175nXqtAvpyuULd+6YewRuiVP8Ut
 jXltu98KX/+aK57deogWxEWThUtzNeWxniQfYAyyClHNNhP7JG8nz2qle/HHTKSQoI93
 vq5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-transfer-encoding;
 bh=OYTrh5g5Dg1lHjwbtOGL94Ip4WGe9pRX4Okm0mk4hyI=;
 b=cDqTIWEIEIChfaPSzjd5rq71Dyf+RcSNUs10FoG6BedbZ+Ii1dSZEZQwfTz+Lfm3Ho
 tSo7j9ldSANxZoyGNE1i9G6TY5pm1SZBzJVUujomOXwi53Z1kACdmsN3SIX0pLf6XBKl
 rIga6IwEVHs9UUOh4TXoXIEbM1IIIA5UJK4xa6gseFZmpEyG4OwxjnU+m6UPt1Fd7ytE
 dpZwnN+n/M2v8m8DYKipl3/+cfvpaMJ12j6d2Yv4rYy/tbY6TK0Tz/vcgQ4E+A1UPlgP
 Hab3gpJoR0sz/osk0Ch8b68LtoTR7xyOhvAwQRaE5ic+OFwaiti5vFp0+QVzwLjl44WP
 A4fg==
X-Gm-Message-State: AOAM5329bMtRujWLgsOmiDlE2Nb3KciJt2O4akq5R9Hx0WgwL19IrEg5
 n0HxQXAVRE6asnhmcIFZHbA=
X-Google-Smtp-Source: ABdhPJzBvV5Q7cRvsqDCThSGCWCE9ZqYML+emOC0Lxo/tdT+kwg8vRBU7QhPydXEJQAFQvTCYsENsQ==
X-Received: by 2002:a2e:9149:0:b0:249:84ee:23fa with SMTP id
 q9-20020a2e9149000000b0024984ee23famr6547127ljg.196.1649282603204; 
 Wed, 06 Apr 2022 15:03:23 -0700 (PDT)
Received: from sovereign (broadband-37-110-65-23.ip.moscow.rt.ru.
 [37.110.65.23]) by smtp.gmail.com with ESMTPSA id
 m18-20020a056512359200b00450e1840e80sm889494lfr.247.2022.04.06.15.03.22
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Wed, 06 Apr 2022 15:03:22 -0700 (PDT)
Date: Thu, 7 Apr 2022 01:03:21 +0300
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org, Vipin
 Varghese <vipin.varghese@amd.com>, Ciara Power <ciara.power@intel.com>,
 Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>, Tyler Retzlaff
 <roretzla@linux.microsoft.com>, Narcisa Ana Maria Vasile
 <navasile@linux.microsoft.com>, Dmitry Malloy <dmitrym@microsoft.com>,
 Pallavi Kadam <pallavi.kadam@intel.com>
Subject: Re: [RFC] Telemetry enhancements and Windows support
Message-ID: <20220407010321.3e7efa17@sovereign>
In-Reply-To: <20220406145733.4017b0fb@hermes.local>
References: <20220402015901.72798593@sovereign>
 <YkrCWUS6p4VHQfH8@bricha3-MOBL.ger.corp.intel.com>
 <20220407005029.29e34a11@sovereign>
 <20220406145733.4017b0fb@hermes.local>
X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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

2022-04-06 14:57 (UTC-0700), Stephen Hemminger:
> On Thu, 7 Apr 2022 00:50:29 +0300
> Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> wrote:
> 
> > 2022-04-04 11:03 (UTC+0100), Bruce Richardson:
> > [...]  
> > > Having EAL be the only one to create threads seems reasonable. However, I'm
> > > a little uncertain about the scope of change and tying telemetry and EAL
> > > together a lot more.    
> > 
> > Scope is a strong valid argument.
> > What do you think if telemetry would create threads using Win32 API
> > just like on Unices it creates threads using pthread
> > (external component that is always present)?  
> 
> Why isn't telemetry using existing rte_ctrl_thread API?

It would depend on EAL at link time then.
But EAL already depends on telemetry and there would be a loop.