DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Mattias Rönnblom" <hofors@lysator.liu.se>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: EAL threads
Date: Wed, 21 Sep 2022 10:05:36 +0100	[thread overview]
Message-ID: <YyrT4NDsmsT5J1IE@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <2af5b047-f5fb-3074-9d8e-8dd7b01ce3c1@lysator.liu.se>

On Wed, Sep 21, 2022 at 10:39:15AM +0200, Mattias Rönnblom wrote:
> I have some lcore-related questions:
> 
> The documentation make use of the term "non-EAL thread". Is a non-EAL thread
> the same thing as a non-lcore thread? I.e., are there EAL threads that are
> not lcore threads?

Yes, there are some threads created by EAL which are not lcore threads.
These are generally for background tasks, such as interrupts or telemetry,
and are given a coremask to be kept away from the dataplane lcore threads.
Therefore, I think you are right to try and get clear terminology for the
threads. In most cases, I think non-EAL thread is referring to threads
created by the app itself, but it may in some cases refer to the 'non-lcore
threads' as you call them.

Personally, I would suggest terms like:
* dataplane threads
* background eal threads
* app threads

for clarity, since I think the term EAL thread is ambiguous. However,
you or others might have been ideas for terms.

> 
> I also have a question related to rte_register_thread(): shouldn't the
> documentation say the user is assumed to pin the calling thread to some
> core? That is the expectation, correct?

Probably, but it's not mandatory.

  reply	other threads:[~2022-09-21  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21  8:39 Mattias Rönnblom
2022-09-21  9:05 ` Bruce Richardson [this message]
2022-09-21 10:36   ` Morten Brørup
2022-09-30 20:49   ` 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=YyrT4NDsmsT5J1IE@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hofors@lysator.liu.se \
    /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).