From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: David Marchand <david.marchand@redhat.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: "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: Thu, 1 Jun 2023 12:23:39 +0000 [thread overview]
Message-ID: <DM4PR11MB5994E39D817524BC773F3900D7499@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8wgvxA+k3Qt5QqJtJKR+UYfEzWvGSfCaWPnGB7WtV03Jg@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Thursday, June 1, 2023 4:50 PM
> To: Richardson, Bruce <bruce.richardson@intel.com>; Tyler Retzlaff
> <roretzla@linux.microsoft.com>
> Cc: dev@dpdk.org; thomas@monjalon.net; Zhang, Qi Z
> <qi.z.zhang@intel.com>
> Subject: Re: [PATCH 0/6] windows: remove most pthread lifetime shim
> functions
>
> On Tue, Apr 18, 2023 at 11:21 AM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > On Sun, Apr 02, 2023 at 10:34:12PM -0700, Tyler Retzlaff wrote:
> > > early review if possible please, would like to have this in from the
> > > start of 23.07 to work against.
> > >
> > > thanks!
> > >
> >
> > Don't see any problems with this set.
>
> Drivers maintainers were not copied (Tyler, git send-email has options --to-
> cmd or --cc-cmd to which you can pass ./devtools/get-maintainers.sh).
> I pinged Qi during the maintainers call today.
Hi Tyler & David:
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.
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?
Thanks
Qi
>
> The changes are straightforward and lgtm.
> For the series,
> Reviewed-by: David Marchand <david.marchand@redhat.com>
>
>
> --
> David Marchand
next prev parent reply other threads:[~2023-06-01 12:23 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 [this message]
2023-06-02 16:22 ` Tyler Retzlaff
2023-06-09 12:38 ` David Marchand
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=DM4PR11MB5994E39D817524BC773F3900D7499@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).