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 30269A034C;
	Thu, 28 Apr 2022 14:01:05 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id D9BA442820;
	Thu, 28 Apr 2022 14:01:00 +0200 (CEST)
Received: from mail-vk1-f174.google.com (mail-vk1-f174.google.com
 [209.85.221.174])
 by mails.dpdk.org (Postfix) with ESMTP id EA0BA406A2
 for <dev@dpdk.org>; Tue, 26 Apr 2022 21:11:24 +0200 (CEST)
Received: by mail-vk1-f174.google.com with SMTP id e7so9197246vkh.2
 for <dev@dpdk.org>; Tue, 26 Apr 2022 12:11:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=NPU2vXVuBX/0MPfvQDN2Ta6u4Iucb/E8ltZV63FFEtI=;
 b=R6W3Hps6fm3ZocOKS8ZgNNhfg0V2zOKsj8T6LrL5j5O55NSZHGpZnY7c773V/3QlwB
 S11dsr7rdGfyBxt74edmx3dq+Pg1wUpMuHJIk4xrVZeWrtRCxqJQsSCv9u5jd3HAjARB
 vcGLABf3pMqUNOkUr+wH/WVR87okGklzuDTqt6wxWta/hC9MjEcyaICJGHiz6vhkdCha
 meJ9h59gRkqHY0NpU7636x5LSG4aRNjm8xv28zNUor23tfo9JxjpMOfqGW3gT4mgpg4U
 I60NkwI90iERX+lZ8QUX51sYeSYa0n84VALnTHNdtFGRFo88XOqhr7z/Ud6KjgI4ymN3
 1n0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=NPU2vXVuBX/0MPfvQDN2Ta6u4Iucb/E8ltZV63FFEtI=;
 b=6D1/QjVM//JHgBV2tC7PIzmy+wazomFYrph726SoS/PQ2y3MCexIhTUUUM6wQxRGRC
 VrucgjRc1zZVwAVnlNw24pTBMxbgUQFeu/XWFjSUIIhoSutzEyL1Ol7ph9TLH1p0MHA3
 4ccG1VXeu+cVL+52UbP5b0JUV1xKkETqueX9X0+x1PjDabs0KR9DFz7KKGgCNunJ7Msg
 lbMsmJui0ZuGzIS7+BONG+GsD+gOfRAyn++bOmVhaBbMSBTeOMfYkjNAF6bWSCgrm+os
 H8Dkc2mIzBcD81guwLPTLZZLd3dKIZMAAXaOAOefiNZ2MYoC0NxHaJe4XfnYtq4R7F+I
 PJUQ==
X-Gm-Message-State: AOAM531jdhpuZIwilJcGMjPc9uGLMeKIrqOuwpDOzwC8bcxo14TSf7M6
 O+4vYhelYEJsmQhsjtwETvXGjboDVnEErLpvbE5AVFh6
X-Google-Smtp-Source: ABdhPJz8naDlS+KH2LDuNs297aQrCCtV6lkal7y695ICknFiL2VqUMn/CUdCozZNxaZoZTgoYcCllvpQmjEG07Zm4HE=
X-Received: by 2002:a1f:4dc3:0:b0:345:e63c:59df with SMTP id
 a186-20020a1f4dc3000000b00345e63c59dfmr7541557vkb.36.1651000284166; Tue, 26
 Apr 2022 12:11:24 -0700 (PDT)
MIME-Version: 1.0
References: <CAPA_rBc6txyOQ+P2-eVWCRuxCnE-AL1_kMyujtob8GzScX=WsQ@mail.gmail.com>
 <20220426075600.3598119f@hermes.local>
In-Reply-To: <20220426075600.3598119f@hermes.local>
From: Ansar Kannankattil <ansarkannankat@gmail.com>
Date: Wed, 27 Apr 2022 00:41:12 +0530
Message-ID: <CAPA_rBf2fRG9GGMNYT2khws-3GA1TL9LBCq+-rBLpKOg9tCddA@mail.gmail.com>
Subject: Re: Reuse Of lcore after returning from its worker thread
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Content-Type: multipart/alternative; boundary="000000000000763ee405dd9375d6"
X-Mailman-Approved-At: Thu, 28 Apr 2022 14:00:58 +0200
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

--000000000000763ee405dd9375d6
Content-Type: text/plain; charset="UTF-8"

But how the state is changed to WAIT once the worker thread function
returned

On Tue, 26 Apr, 2022, 8:26 pm Stephen Hemminger, <stephen@networkplumber.org>
wrote:

> On Wed, 20 Apr 2022 17:52:20 +0530
> Ansar Kannankattil <ansarkannankat@gmail.com> wrote:
>
> > Hi,
> > As per my understanding "*rte_eal_wait_lcore" *is a blocking call in case
> > of lcore state running.
> > 1. Is there any direct way to reuse the lcore which we returned from a
> > worker thread?
> > 2. Technically is there any issue in reusing the lcore by some means?
>
> Yes just relaunch with new work function.
>

--000000000000763ee405dd9375d6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">But how the state is changed to WAIT once the worker thre=
ad function returned</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Tue, 26 Apr, 2022, 8:26 pm Stephen Hemminger, &lt;<a=
 href=3D"mailto:stephen@networkplumber.org">stephen@networkplumber.org</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, 20 Apr 2022 17:5=
2:20 +0530<br>
Ansar Kannankattil &lt;<a href=3D"mailto:ansarkannankat@gmail.com" target=
=3D"_blank" rel=3D"noreferrer">ansarkannankat@gmail.com</a>&gt; wrote:<br>
<br>
&gt; Hi,<br>
&gt; As per my understanding &quot;*rte_eal_wait_lcore&quot; *is a blocking=
 call in case<br>
&gt; of lcore state running.<br>
&gt; 1. Is there any direct way to reuse the lcore which we returned from a=
<br>
&gt; worker thread?<br>
&gt; 2. Technically is there any issue in reusing the lcore by some means?<=
br>
<br>
Yes just relaunch with new work function.<br>
</blockquote></div>

--000000000000763ee405dd9375d6--