From: David Marchand <david.marchand@redhat.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [PATCH 0/6] windows: remove most pthread lifetime shim functions
Date: Fri, 9 Jun 2023 14:38:41 +0200 [thread overview]
Message-ID: <CAJFAV8yYkQcgbjUtyrjOp0b7kEF_tmKKeUe1W4FTQ8A5fXcJcQ@mail.gmail.com> (raw)
In-Reply-To: <20230602162208.GA12490@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Fri, Jun 2, 2023 at 6:22 PM Tyler Retzlaff
<roretzla@linux.microsoft.com> wrote:
> On Thu, Jun 01, 2023 at 12:23:39PM +0000, Zhang, Qi Z wrote:
> > The patchset looks good to me.
> >
> > I have just one question regarding the patch set targets, which include PMD iavf, ice, and ixgbe. However, I noticed that some other Intel PMDs like ipn3ke still use rte_ctrl_thread_create and have not been replaced.
>
> The series really isn't about rte_ctrl_thread_create, it just happens
> that for code built on Windows that code needs to stop using
> rte_ctrl_thread_create because it references the pthread shim that is
> being removed.
>
> At some point in the future (it's lower priority right now) I will
> submit a series that converts all rte_ctrl_thread_create ->
> rte_control_thread_create since rte_ctrl_thread_create is being
> deprecated.
>
> >
> > I assume that this replacement is specifically intended for PMDs that support Windows, as PMDs with the "Windows" feature should be covered. However, I didn't see the "Windows" feature enabled for iavf PMD, even though it is included in the patch set.
> >
> > Could you help me understand the criteria used for determining which PMDs should be included in this replacement?
>
> Yes, you are correct the patch is intended to address PMDs / code built
> on Windows specifically. I just re-verified that iavf is being built
> for Windows.
>
> If I remove the iavf patch from the series I get the following warning,
> so that is why I adapted the iavf PMD code.
>
> [249/749] Compiling C object
> drivers/libtmp_rte_net_iavf.a.p/net_iavf_iavf_vchnl.c.obj
> ../drivers/net/iavf/iavf_vchnl.c:162:2: warning: implicit declaration of
> function 'pthread_join' is invalid in C99
> [-Wimplicit-function-declaration]
> pthread_join(handler->tid, NULL);
>
> >
> > Thanks
> > Qi
> >
> > >
> > > The changes are straightforward and lgtm.
> > > For the series,
> > > Reviewed-by: David Marchand <david.marchand@redhat.com>
>
> I think with the above explained the series should be okay as is, no
> changes required if Qi is okay with the above explanation.
Which seems to be the case.
Thank you.
--
David Marchand
next prev parent reply other threads:[~2023-06-09 12:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 22:34 Tyler Retzlaff
2023-03-17 22:34 ` [PATCH 1/6] dma/skeleton: use rte thread API Tyler Retzlaff
2023-04-18 9:19 ` Bruce Richardson
2023-04-18 15:04 ` Tyler Retzlaff
2023-03-17 22:34 ` [PATCH 2/6] net/ixgbe: " Tyler Retzlaff
2023-03-17 22:34 ` [PATCH 3/6] net/ice: " Tyler Retzlaff
2023-03-17 22:34 ` [PATCH 4/6] net/iavf: " Tyler Retzlaff
2023-03-17 22:34 ` [PATCH 5/6] eal: " Tyler Retzlaff
2023-03-17 22:34 ` [PATCH 6/6] windows: remove most pthread lifetime shim functions Tyler Retzlaff
2023-04-03 5:34 ` [PATCH 0/6] " Tyler Retzlaff
2023-04-18 9:21 ` Bruce Richardson
2023-06-01 8:49 ` David Marchand
2023-06-01 12:23 ` Zhang, Qi Z
2023-06-02 16:22 ` Tyler Retzlaff
2023-06-09 12:38 ` David Marchand [this message]
2023-04-17 16:46 ` Tyler Retzlaff
2023-06-09 12:39 ` David Marchand
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=CAJFAV8yYkQcgbjUtyrjOp0b7kEF_tmKKeUe1W4FTQ8A5fXcJcQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=roretzla@linux.microsoft.com \
--cc=thomas@monjalon.net \
/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).