From: David Marchand <david.marchand@redhat.com>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Cc: Ray Kinsella <mdr@ashroe.eu>, Neil Horman <nhorman@tuxdriver.com>,
dev <dev@dpdk.org>,
tomasz.piatkowski@ericsson.com, nd <nd@arm.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Van Haaren Harry <harry.van.haaren@intel.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Subject: Re: [dpdk-dev] [RFC] eal: introduce function to get lcore thread id
Date: Tue, 20 Oct 2020 15:38:51 +0200 [thread overview]
Message-ID: <CAJFAV8we-O5K02g+RF4P=Y-h7pVqVsVGTm0Mm9joyC6N4Awajw@mail.gmail.com> (raw)
In-Reply-To: <20200810093652.102078-1-mattias.ronnblom@ericsson.com>
On Mon, Aug 10, 2020 at 11:37 AM Mattias Rönnblom
<mattias.ronnblom@ericsson.com> wrote:
>
> Introduce function in <rte_lcore.h> to retrieve a lcore worker
> thread's pthread id.
>
> This change allows applications to do things like changing the name of
> a lcore thread, or detect if it's getting interrupted (e.g. getting
> preempted by another thread).
>
> Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
I can see no feedback.
I am a bit reluctant at giving access to this info which is not really
abstracted across OS..
Is there no other way to achieve what you wanted?
--
David Marchand
next prev parent reply other threads:[~2020-10-20 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 12:03 [dpdk-dev] Retrieving lcore worker " Mattias Rönnblom
2020-07-14 13:08 ` Van Haaren, Harry
2020-07-14 18:59 ` Honnappa Nagarahalli
2020-07-14 20:51 ` Stephen Hemminger
2020-07-15 10:17 ` Mattias Rönnblom
2020-07-15 16:21 ` Stephen Hemminger
2020-07-16 10:20 ` Mattias Rönnblom
2020-08-10 9:36 ` [dpdk-dev] [RFC] eal: introduce function to get lcore " Mattias Rönnblom
2020-10-20 13:38 ` David Marchand [this message]
2020-10-20 18:40 ` Mattias Rönnblom
2020-07-15 10:21 ` [dpdk-dev] Retrieving lcore worker " 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='CAJFAV8we-O5K02g+RF4P=Y-h7pVqVsVGTm0Mm9joyC6N4Awajw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=harry.van.haaren@intel.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=mdr@ashroe.eu \
--cc=nd@arm.com \
--cc=nhorman@tuxdriver.com \
--cc=stephen@networkplumber.org \
--cc=tomasz.piatkowski@ericsson.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).