DPDK usage discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: Can a DPDK API like rte_eth_dev_set_mtu be called by a normal pthread
Date: Tue, 23 Aug 2022 13:22:45 +0300	[thread overview]
Message-ID: <20220823132245.5a9f9876@sovereign> (raw)
In-Reply-To: <CAO8pfFnekCRktTBLPdbVwUrpsphqmMRsEOg-fQkYMRPDz9XgaQ@mail.gmail.com>

2022-08-23 11:25 (UTC+0200), Antonio Di Bacco:
> I have a DPDK process that also creates a normal pthread, is there
> anything wrong to call a DPDK api from this normal pthread?

Nothing wrong, this is allowed.

You may be interested in rte_thread_register(),
if you want to consider this thread as an lcore.
Also, rte_socket_id() will return SOCKET_ID_ANY
unless the thread is registered, for example.

  reply	other threads:[~2022-08-23 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23  9:25 Antonio Di Bacco
2022-08-23 10:22 ` Dmitry Kozlyuk [this message]
2022-08-23 11:57   ` Antonio Di Bacco
2022-08-23 12:08     ` Dmitry Kozlyuk
2022-08-30 15:25       ` Antonio Di Bacco

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=20220823132245.5a9f9876@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=a.dibacco.ks@gmail.com \
    --cc=users@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 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).