All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ansar Kannankattil <ansarkannankat@gmail.com>
Cc: dev@dpdk.org
Subject: Re: Reuse Of lcore after returning from its worker thread
Date: Tue, 26 Apr 2022 07:56:00 -0700	[thread overview]
Message-ID: <20220426075600.3598119f@hermes.local> (raw)
In-Reply-To: <CAPA_rBc6txyOQ+P2-eVWCRuxCnE-AL1_kMyujtob8GzScX=WsQ@mail.gmail.com>

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.

  reply	other threads:[~2022-04-26 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 12:22 Reuse Of lcore after returning from its worker thread Ansar Kannankattil
2022-04-26 14:56 ` Stephen Hemminger [this message]
2022-04-26 19:11   ` Ansar Kannankattil

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=20220426075600.3598119f@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=ansarkannankat@gmail.com \
    --cc=dev@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.