From: Stephen Hemminger <stephen@networkplumber.org>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
dev@dpdk.org, Vipin Varghese <vipin.varghese@amd.com>,
Ciara Power <ciara.power@intel.com>,
Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
Dmitry Malloy <dmitrym@microsoft.com>,
Pallavi Kadam <pallavi.kadam@intel.com>
Subject: Re: [RFC] Telemetry enhancements and Windows support
Date: Wed, 6 Apr 2022 14:57:33 -0700 [thread overview]
Message-ID: <20220406145733.4017b0fb@hermes.local> (raw)
In-Reply-To: <20220407005029.29e34a11@sovereign>
On Thu, 7 Apr 2022 00:50:29 +0300
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> wrote:
> 2022-04-04 11:03 (UTC+0100), Bruce Richardson:
> [...]
> > Having EAL be the only one to create threads seems reasonable. However, I'm
> > a little uncertain about the scope of change and tying telemetry and EAL
> > together a lot more.
>
> Scope is a strong valid argument.
> What do you think if telemetry would create threads using Win32 API
> just like on Unices it creates threads using pthread
> (external component that is always present)?
Why isn't telemetry using existing rte_ctrl_thread API?
next prev parent reply other threads:[~2022-04-06 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 22:59 Dmitry Kozlyuk
2022-04-02 0:55 ` Dmitry Kozlyuk
2022-04-04 10:03 ` Bruce Richardson
2022-04-06 21:50 ` Dmitry Kozlyuk
2022-04-06 21:57 ` Stephen Hemminger [this message]
2022-04-06 22:03 ` Dmitry Kozlyuk
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=20220406145733.4017b0fb@hermes.local \
--to=stephen@networkplumber.org \
--cc=Sivaprasad.Tummala@amd.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=roretzla@linux.microsoft.com \
--cc=vipin.varghese@amd.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).