DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org, harini.ramakrishnan@microsoft.com
Cc: eilong@mellanox.com, pallavi.kadam@intel.com,
	ranjit.menon@intel.com, ocardona@microsoft.com,
	shshaikh@marvell.com, nareshkumar.pbs@broadcom.com,
	ravianan@cisco.com, talshn@mellanox.com, hgani@marvell.com,
	rksaripa@cisco.com, narcisa.vasile@microsoft.com,
	dmitry.kozliuk@gmail.com, u9012063@gmail.com,
	ophirmu@mellanox.com, thasreef@chelsio.com
Subject: [dpdk-web] [PATCH] add roadmap for Windows
Date: Wed, 19 Feb 2020 22:26:02 +0100	[thread overview]
Message-ID: <20200219212602.2332159-1-thomas@monjalon.net> (raw)

Initial DPDK PMD support is planned for LTS release 20.11.

Broadcom, Chelsio, Cisco, Intel, Marvell, Mellanox, Microsoft,
and all volunteers are welcomed joining this effort.

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---

This page will appear at http://core.dpdk.org/roadmap/windows/
If no comment by the end of this week, it will be published.

Please do not hesitate to suggest rewords or additions,
especially for vendor-specific steps for a PMD.

---
 content/roadmap/windows.md | 103 +++++++++++++++++++++++++++++++++++++
 1 file changed, 103 insertions(+)
 create mode 100644 content/roadmap/windows.md

diff --git a/content/roadmap/windows.md b/content/roadmap/windows.md
new file mode 100644
index 0000000..03bef68
--- /dev/null
+++ b/content/roadmap/windows.md
@@ -0,0 +1,103 @@
++++
+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:
+
+- [dpdk](//git.dpdk.org/dpdk/)
+- [dpdk-kmods](//git.dpdk.org/dpdk-kmods/)
+
+The [DPDK documentation for Windows](//doc.dpdk.org/guides/windows_gsg/)
+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}
+----
+
+{{% notice info %}}
+Features and milestones may be noted here.
+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-lcore variables with shared libraries
+- 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
+
+- EAL basic memory management
+- PCI general probing
+- PCI bifurcated model
+- netuio source code hosting
+- netuio binary hosting
+- netuio documentation
+
+#### 2020-05-01
+
+- EAL advanced memory management
+- PCI netuio model
+- mempool
+- cmdline
+- Mellanox DevX library
+
+#### 2020-06-01
+
+- mbuf
+- ethdev
+- Mellanox glue layer
+
+#### 2020-07-01
+
+- testpmd
+- ring PMD
+- pcap or other vdev PMD
+- optionnally virtio PMD
+
+#### 2020-08-01
+
+- Broadcom bnxt PMD Rx/Tx
+- Chelsio cxgbe PMD Rx/Tx
+- Cisco enic PMD Rx/Tx
+- Intel i40e PMD Rx/Tx
+- Marvell qede PMD Rx/Tx
+- Mellanox mlx5 PMD Rx/Tx
+- Mellanox documentation
+
+#### 2020-09-01
+
+- Mellanox rte_flow features
+- Functional tests in CI
+
+#### 2020-10-01
+
+- only bug fixing after this point
+
+#### 2020-11-01
+
+- DPDK 20.11 LTS release
+
+#### Future {#future}
+
+- Intel ice PMD
+- multi-process support
-- 
2.25.0


             reply	other threads:[~2020-02-19 21:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 21:26 Thomas Monjalon [this message]
2020-02-25  9:16 ` 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=20200219212602.2332159-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=eilong@mellanox.com \
    --cc=harini.ramakrishnan@microsoft.com \
    --cc=hgani@marvell.com \
    --cc=narcisa.vasile@microsoft.com \
    --cc=nareshkumar.pbs@broadcom.com \
    --cc=ocardona@microsoft.com \
    --cc=ophirmu@mellanox.com \
    --cc=pallavi.kadam@intel.com \
    --cc=ranjit.menon@intel.com \
    --cc=ravianan@cisco.com \
    --cc=rksaripa@cisco.com \
    --cc=shshaikh@marvell.com \
    --cc=talshn@mellanox.com \
    --cc=thasreef@chelsio.com \
    --cc=u9012063@gmail.com \
    --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).