From: "Shukla, Shivanshu" <shivanshu.shukla@intel.com>
To: "Kadam, Pallavi" <pallavi.kadam@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"fady@mellanox.com" <fady@mellanox.com>,
"Narcisa.Vasile@microsoft.com" <Narcisa.Vasile@microsoft.com>,
"dmitry.kozliuk@gmail.com" <dmitry.kozliuk@gmail.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Menon, Ranjit" <ranjit.menon@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/3] Support iavf PMD on Windows
Date: Mon, 27 Sep 2021 14:33:53 -0700 [thread overview]
Message-ID: <69b7837c-e2af-73d6-dda7-252f0afd1408@intel.com> (raw)
In-Reply-To: <20210909232321.5091-1-pallavi.kadam@intel.com>
On 9/9/2021 4:23 PM, Kadam, Pallavi wrote:
> This patch-set enables building the iavf PMD on Windows.
> Currently, it uses alarm functions so, depends on following series.
>
> Depends-on: series-18447 ("net/iavf: enable interrupt polling")
>
> v3 changes:
> - Fix doc build warning
> v2 changes:
> - Rebase for 21.11
> - Fix for 'random'
>
> Pallavi Kadam (3):
> net/iavf: build on Windows
> lib/net: fix support of random
> doc: update iavf PMD and 21.11 release notes
>
> doc/guides/nics/intel_vf.rst | 18 ++++++++++++++++++
> doc/guides/rel_notes/release_21_11.rst | 4 ++++
> drivers/net/iavf/iavf.h | 3 ++-
> drivers/net/iavf/iavf_rxtx_vec_avx2.c | 2 +-
> drivers/net/iavf/iavf_rxtx_vec_avx512.c | 2 +-
> drivers/net/iavf/iavf_tm.c | 2 +-
> drivers/net/iavf/meson.build | 9 ++++-----
> lib/net/rte_ether.c | 4 ----
> 8 files changed, 31 insertions(+), 13 deletions(-)
>
> --
Acked-by: Shivanshu Shukla <shivanshu.shukla@intel.com>
next prev parent reply other threads:[~2021-09-27 23:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 23:08 [dpdk-dev] [PATCH] net/iavf: enable " Pallavi Kadam
2021-09-09 20:05 ` [dpdk-dev] [PATCH v2 0/3] Support iavf PMD " Pallavi Kadam
2021-09-09 20:05 ` [dpdk-dev] [PATCH v2 1/3] net/iavf: build " Pallavi Kadam
2021-09-09 20:05 ` [dpdk-dev] [PATCH v2 2/3] lib/net: fix support of random Pallavi Kadam
2021-09-09 20:05 ` [dpdk-dev] [PATCH v2 3/3] doc: update iavf PMD and 21.11 release notes Pallavi Kadam
2021-09-09 23:23 ` [dpdk-dev] [PATCH v3 0/3] Support iavf PMD on Windows Pallavi Kadam
2021-09-09 23:23 ` [dpdk-dev] [PATCH v3 1/3] net/iavf: build " Pallavi Kadam
2021-09-22 20:58 ` Shukla, Shivanshu
2021-09-09 23:23 ` [dpdk-dev] [PATCH v3 2/3] lib/net: fix support of random Pallavi Kadam
2021-09-22 21:00 ` Shukla, Shivanshu
2021-09-30 16:46 ` Thomas Monjalon
2021-09-30 22:36 ` Kadam, Pallavi
2021-09-09 23:23 ` [dpdk-dev] [PATCH v3 3/3] doc: update iavf PMD and 21.11 release notes Pallavi Kadam
2021-09-22 21:01 ` Shukla, Shivanshu
2021-09-30 16:49 ` Thomas Monjalon
2021-09-30 19:07 ` Thomas Monjalon
2021-09-22 20:56 ` [dpdk-dev] [PATCH v3 0/3] Support iavf PMD on Windows Shukla, Shivanshu
2021-09-22 20:58 ` Shukla, Shivanshu
2021-09-27 21:33 ` Shukla, Shivanshu [this message]
2021-09-30 20:15 ` Thomas Monjalon
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=69b7837c-e2af-73d6-dda7-252f0afd1408@intel.com \
--to=shivanshu.shukla@intel.com \
--cc=Narcisa.Vasile@microsoft.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=fady@mellanox.com \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@intel.com \
--cc=pallavi.kadam@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=ranjit.menon@intel.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).