From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: dev@dpdk.org
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Ranjit Menon <ranjit.menon@intel.com>,
Pallavi Kadam <pallavi.kadam@intel.com>,
Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>,
Narcisa Ana Maria Vasile <narcisa.vasile@microsoft.com>,
William Tu <u9012063@gmail.com>
Subject: [dpdk-dev] [RFC PATCH 0/5] virtio-net support for Windows draft
Date: Fri, 28 Feb 2020 09:07:22 +0300 [thread overview]
Message-ID: <20200228060727.192491-1-dmitry.kozliuk@gmail.com> (raw)
In-Reply-To: <20200227071126.75162e92@Sovereign>
This patchset provides reference of the changes made to run virtio-net PMD
with Windows draft DPDK, so that this could be reproduced. Is is not
intended to be merged neither soon, nor "as is".
Patches must be applied over "multi-BAR" patchset yet to be released by
Microsoft, those patches are not included. After applying Microsoft
patches, the whole drivers/net/virtio directory from upstream v18.08
must be imported. It is also not included for brevity.
Dmitry Kozlyuk (5):
pci/windows: add stubs for port IO
net: add stub for RARP packet generation on Windows
pci/windows: split config I/O into series of fixed-size operations
netuio: change class for Net to custom
mk/windows: add virtio-net PMD
drivers/bus/pci/windows/pci.c | 80 +-
drivers/net/virtio/virtio_ethdev.c | 4 +
kernel/windows/netuio/netuio.inf | 17 +-
lib/librte_eal/windows/eal/eal.c | 4 +
lib/librte_net/rte_net.c | 12 +
mk/exec-env/windows/dpdk.sln | 754 +++++++++---------
mk/exec-env/windows/l2fwd/l2fwd.vcxproj | 242 +++---
mk/exec-env/windows/l3fwd/l3fwd.vcxproj | 292 +++----
.../librte_pmd_i40e.vcxproj.filters | 198 +++++
.../librte_pmd_net_virtio.vcxproj | 129 +++
10 files changed, 1075 insertions(+), 657 deletions(-)
create mode 100644 mk/exec-env/windows/librte_pmd_net_virtio/librte_pmd_i40e.vcxproj.filters
create mode 100644 mk/exec-env/windows/librte_pmd_net_virtio/librte_pmd_net_virtio.vcxproj
--
2.25.1
next prev parent reply other threads:[~2020-02-28 6:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 8:45 [dpdk-dev] Windows Draft Build Dmitry Kozlyuk
2020-02-10 5:03 ` Ranjit Menon
2020-02-10 6:14 ` Dmitry Kozlyuk
2020-02-17 1:14 ` Dmitry Kozlyuk
2020-02-18 21:44 ` Ranjit Menon
2020-02-25 2:37 ` Dmitry Kozlyuk
2020-02-25 9:06 ` Ranjit Menon
2020-02-26 6:22 ` Dmitry Kozlyuk
2020-02-27 4:11 ` Dmitry Kozlyuk
2020-02-27 15:25 ` William Tu
2020-02-27 15:42 ` David Marchand
2020-02-28 6:07 ` Dmitry Kozlyuk [this message]
2020-02-28 6:07 ` [dpdk-dev] [RFC PATCH 1/5] pci/windows: add stubs for port IO Dmitry Kozlyuk
2020-02-28 6:07 ` [dpdk-dev] [RFC PATCH 2/5] net: add stub for RARP packet generation on Windows Dmitry Kozlyuk
2020-02-28 6:07 ` [dpdk-dev] [RFC PATCH 3/5] pci/windows: split config I/O into series of fixed-size operations Dmitry Kozlyuk
2020-02-28 6:07 ` [dpdk-dev] [RFC PATCH 4/5] netuio: change class for Net to custom Dmitry Kozlyuk
2020-02-28 6:07 ` [dpdk-dev] [RFC PATCH 5/5] mk/windows: add virtio-net PMD Dmitry Kozlyuk
2021-08-14 15:55 ` William Tu
2021-08-14 17:00 ` Dmitry Kozlyuk
2021-08-15 14:28 ` William Tu
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=20200228060727.192491-1-dmitry.kozliuk@gmail.com \
--to=dmitry.kozliuk@gmail.com \
--cc=dev@dpdk.org \
--cc=harini.ramakrishnan@microsoft.com \
--cc=narcisa.vasile@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=u9012063@gmail.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).