DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: Markus Theil <markus.theil@tu-ilmenau.de>,
	dev@dpdk.org, Michael Pfeiffer <michael.pfeiffer@tu-ilmenau.de>,
	Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: [PATCH v2 1/2] eal: expose lcore pthread id
Date: Thu, 20 Oct 2022 08:36:05 -0700	[thread overview]
Message-ID: <20221020083605.274c43f2@hermes.local> (raw)
In-Reply-To: <CAJFAV8yZf9J0Pj8YoVe1_dMthV-HVHhUTFfQSQivuA26G43sAA@mail.gmail.com>

On Thu, 20 Oct 2022 13:20:40 +0200
David Marchand <david.marchand@redhat.com> wrote:

> On Fri, Oct 14, 2022 at 9:54 AM Markus Theil <markus.theil@tu-ilmenau.de> wrote:
> >
> > From: Michael Pfeiffer <michael.pfeiffer@tu-ilmenau.de>
> >
> > Also expose the pthread id of each lcore, in
> > order to allow modification of pthread attributes,
> > for example use rte_thread_setname without executing
> > pthread_self() on the maybe already running lcore.
> >
> > The rte_lcore_to_thread_id function is added to API.
> >
> > Signed-off-by: Michael Pfeiffer <michael.pfeiffer@tu-ilmenau.de>  
> 
> We are trying to abstract the use of pthread in DPDK API.
> So I don't think this patch is going in the right direction.

Agree, exposing this will make Windows support harder
and who knows what next OS to come will need.

  reply	other threads:[~2022-10-20 15:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  6:20 [PATCH " Markus Theil
2022-10-14  6:21 ` [PATCH 2/2] eal: prevent OOB read in rte_lcore_to_socket_id Markus Theil
2022-10-14  7:54 ` [PATCH v2 1/2] eal: expose lcore pthread id Markus Theil
2022-10-14  7:54   ` [PATCH v2 2/2] eal: prevent OOB read in rte_lcore_to_socket_id Markus Theil
2022-10-20 11:20   ` [PATCH v2 1/2] eal: expose lcore pthread id David Marchand
2022-10-20 15:36     ` Stephen Hemminger [this message]
2022-10-20 20:03       ` Michael Pfeiffer
2022-11-29 22:04         ` Tyler Retzlaff
2023-07-06  2:57           ` Stephen Hemminger
2023-07-06  5:50             ` Michael Pfeiffer
2022-11-12  0:34       ` Tyler Retzlaff

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=20221020083605.274c43f2@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=markus.theil@tu-ilmenau.de \
    --cc=michael.pfeiffer@tu-ilmenau.de \
    --cc=roretzla@linux.microsoft.com \
    /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).