DPDK website maintenance
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: web@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>,
	Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Subject: [dpdk-web] [PATCH] update Windows roadmap
Date: Fri, 27 Aug 2021 03:27:27 +0300	[thread overview]
Message-ID: <20210827002727.113426-1-dmitry.kozliuk@gmail.com> (raw)

Add the current status and the actual roadmap, remove completed entries.
More detailed plan in the mailing list:
https://mails.dpdk.org/archives/dev/2021-August/217463.html

Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
---
 content/roadmap/windows.md | 134 +++++++++++--------------------------
 1 file changed, 38 insertions(+), 96 deletions(-)

diff --git a/content/roadmap/windows.md b/content/roadmap/windows.md
index 23d0892..e037cf9 100644
--- a/content/roadmap/windows.md
+++ b/content/roadmap/windows.md
@@ -4,11 +4,19 @@ title = "Windows Plan"
 
 ## DPDK porting on Windows
 
-The preparation work is hosted in the
-[Windows draft repository](//git.dpdk.org/draft/dpdk-draft-windows/).
 
-The upstream work is being merged in two repositories,
-splitting userspace and kernel code:
+### Status
+
+Upstream supports running testpmd and examples
+with mlx5, i40e, ice, vmxnet3 HW, or with PCAP virtual device.
+It requires yet unsigned kernel-mode drivers to run (except mlx5).
+Only network some PMDs are currently enabled.
+
+Current focus is friction-less consumption by end-users and supporting more HW.
+Multi-process, and hence dpdk-pdump support is neither available nor scheduled.
+
+[Windows draft repository](//git.dpdk.org/draft/dpdk-draft-windows/)
+is suspended, all development happens in the upstream:
 
 - [dpdk](//git.dpdk.org/dpdk/)
 - [dpdk-kmods](//git.dpdk.org/dpdk-kmods/)
@@ -19,8 +27,8 @@ is updated along with upstream progress.
 The PMD-specific documentation should be updated in the common
 [NIC drivers guide](//doc.dpdk.org/guides/nics/index.html).
 
-### Roadmap for Windows Support {#roadmap}
-----
+
+### Roadmap {#roadmap}
 
 {{% notice info %}}
 Features and milestones may be noted here.
@@ -28,108 +36,42 @@ This is not a commitment but plan of work.
 This list is obviously neither complete nor guaranteed.
 {{% /notice %}}
 
-#### Background Tasks (compilers issues) {#background}
-
-✅ meson with clang + msvc linker: <https://github.com/mesonbuild/meson/pull/6483>
-
-- linking and performance of [per-core variables with shared libraries](//mails.dpdk.org/archives/dev/2020-February/157933.html)
-
-✅ structure alignment: <https://bugs.llvm.org/show_bug.cgi?id=24383>
-
-- AVX bug in gcc: <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412>
-
-#### 2019-05-01
-
-✅ helloworld application with meson+clang
-
-#### 2020-03-01
-
-✅ MinGW integration
-
-✅ EAL common directory split
-
-#### 2020-04-01
-
-✅ virt2phys kmod
-
-#### 2020-05-01
-
-✅ EAL log option
-
-✅ EAL timer
-
-✅ EAL basic memory management
-
-✅ PCI general probing
-
-✅ PCI bifurcated model
-
-✅ cmdline
-
-✅ Mellanox DevX library linkage
-
-#### 2020-06-01
-
-- tracing
-
-✅ mempool
-
-✅ mbuf
-
-✅ netuio source code hosting
-
-- netuio binary hosting
-- netuio documentation
-
-✅ PCI netuio model
-
-✅ Mellanox glue layer
-
-#### 2020-07-01
-
-✅ ethdev
-
-- testpmd
-- ring PMD
-- pcap or other vdev PMD
-- optionnally virtio PMD
-
-#### 2020-08-01
-
-- unit tests (app/test/)
-
-✅ Intel i40e PMD Rx/Tx
-
-✅ Mellanox mlx5 PMD Rx/Tx
-
-#### 2020-09-01
-
-- Functional tests in CI
 
-✅ Mellanox documentation
+#### General Availability
 
-- doc compilation (doxygen + sphinx)
+* Ability to install and consume user-space static build
+    - [Meson 0.58+ issue](https://github.com/mesonbuild/meson/issues/8981)
+    - [pkg-config file for Npcap](https://github.com/nmap/npcap/issues/299)
+* Functional build of user-space libraries and PMDs
+* Process, pipeline, and download area for signed builds of kernel-mode drivers
+    - virt2phys security hardening
 
-✅ usertools/dpdk-devbind.py
 
-#### 2020-12-01
+#### Feature Support
 
-- Mellanox rte_flow features
+* Interrupt handling for netuio
+* Fix for vmxnet3 PMD with VMWare hypervisor
+* virtio PMD
+* ena PMD
+* mlx5 PMD rte_flow features
+* Unit-tests
+* Tracing
+* Documentation build (doxygen + sphinx)
 
-✅ buildtools/pmdinfogen/
 
-✅ usertools/dpdk-telemetry.py
+#### Miscellaneous
 
-#### 2021-02-01
+* Tracing for netuio to simplify troubleshooting for end-users
+* Improved documentation and automated scripts
+* [AVX bug in GCC](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412)
+  (workaround available)
+* Functional tests in CI
 
-✅ DPDK 21.02
 
-#### Future {#future}
+#### Future (unscheduled) {#future}
 
-- advanced memory management
-- multi-process support
+- Advanced memory management: IOMMU, inbox kernel-mode driver
 - Broadcom bnxt PMD
 - Chelsio cxgbe PMD
 - Cisco enic PMD
-- Intel ice PMD
 - Marvell qede PMD
-- 
2.29.3


             reply	other threads:[~2021-08-27  0:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27  0:27 Dmitry Kozlyuk [this message]
2021-09-10 15:42 ` Thomas Monjalon
  -- strict thread matches above, loose matches on Subject: below --
2020-05-13 12:24 Thomas Monjalon
2020-05-24  9:25 ` 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=20210827002727.113426-1-dmitry.kozliuk@gmail.com \
    --to=dmitry.kozliuk@gmail.com \
    --cc=Harini.Ramakrishnan@microsoft.com \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \
    /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).