DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: web@dpdk.org
Subject: Re: [PATCH] update Microsoft roadmap for 23.11
Date: Sat, 12 Aug 2023 16:10:50 +0200	[thread overview]
Message-ID: <2568979.Lt9SDvczpP@thomas> (raw)
In-Reply-To: <1677525232-17905-1-git-send-email-roretzla@linux.microsoft.com>

Hi Tyler,

Would you like to update this roadmap patch for integration?


27/02/2023 20:13, Tyler Retzlaff:
> Originally announced in dpdk-dev mailing list:
>   http://mails.dpdk.org/archives/dev/2023-February/262027.html
> 
> Details revised technical board meeting 2023/02/22
>   http://mails.dpdk.org/archives/dev/2023-February/263516.html
> 
> Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> ---
>  content/roadmap/windows.md | 82 ++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 82 insertions(+)
> 
> diff --git a/content/roadmap/windows.md b/content/roadmap/windows.md
> index 0a4c38a..ffa6e2f 100644
> --- a/content/roadmap/windows.md
> +++ b/content/roadmap/windows.md
> @@ -38,12 +38,94 @@ This list is obviously neither complete nor guaranteed.
>  {{% /notice %}}
>  
>  
> +#### Bringing support for Microsoft Visual Studio on Windows
> +
> +Starting with release 23.07 integration will begin to formally support
> +the Microsoft Visual Studio toolset.

MSVC actually starts in 23.11.

> Patches will be introduced that
> +incrementally phase in full support of the core DPDK libraries, the DPDK
> +unit tests and drivers.
> +
> +The following is a draft plan of work targeting the 23.11 release. The
> +plan is subject to change depending on delays and discussions from the
> +review process. Contributions toward this plan from the community are
> +welcome.
> +
> +1. meson.build Changes
> +
> +Meson does not fully abstract away command line arguments to toolchains
> +so an initial series is available that unblocks the use of MSVC. This
> +change is pre-requisite to undertake subsequent steps.
> +
> +http://patches.dpdk.org/project/dpdk/list/?series=26662
> +
> +2. MSVC CI Pipeline Prerequisite
> +
> +Enablement of the DPDK CI pipeline is fundamental to efficiently
> +progressing porting work for the MSVC toolset. A minimal patch series
> +will be supplied to build the kvargs and telemetry libraries only.
> +
> +3. MSVC CI Pipeline Bootstrap
> +
> +With (2) complete work will be done to onboard CI pipeline for the MSVC
> +toolset. Initially the pipeline will only guarantee compilation but as
> +additional libraries and tests are ported will also allow execution of
> +the DPDK unit tests.
> +
> +4. MSVC EAL porting
> +
> +EAL is pre-requisite for porting all other libraries, drivers and unit
> +tests. Porting of EAL will be broken down into multiple-patch series to
> +address & decouple from the toolchain intrinsics topic.
> +
> +Because EAL depends on atomics the porting of EAL cannot be completed
> +until the DPDK 23.11 release. In the interim abstractions introduced will
> +only have the non-MSVC implementation tested during integration on the
> +relevant platforms.

Plan for atomic has changed a little.

> +
> +5. Unit Test Library Porting
> +
> +In addition to EAL there are several libraries required for the basic
> +DPDK unit test harness. Multiple series will be submitted to port the
> +appropriate libraries to allow the harness to be invoked.
> +
> +6. Unit Test Enablement
> +
> +Fundamental unit tests (typically those testing EAL functionality) will
> +be ported to MSVC. For tests that depend only on EAL this is not expected
> +to require code change but is just re-enabling compilation of the tests
> +allowing them to be built and run.
> +
> +7. MSVC CI Pipeline Test Enablement
> +
> +With initial DPDK unit tests building & passing the CI pipeline will be
> +updated to run the unit tests.
> +
> +8. Driver Porting
> +
> +Candidate drivers will be selected from the set currently built with
> +clang. Multiple series will be submitted (probably per-driver) with
> +changes to port to MSVC.
> +
> +Nearing the 23.11 release timeframe the plan will be reviewed to
> +understand and schedule porting work beyond the 23.11 release.
> +
> +#### Kernel Mode Drivers
> +
> +Concurrent work is in progress by Microsoft to provide functionality
> +by the netuio driver for use by DPDK PMDs in the next release of
> +Windows.

Which Windows release?

> +
> +Partners and providers of hardware & PMDs will be able to use the
> +WHQL certification process to sign driver packages containing PMDs
> +that utilize netuio functionality.

Link to WHQL certification process?

> +
>  #### General Availability
>  
>  * 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)
>  * [Working user-space shared build (DLL)][dll]
> +    - Will be addressed as a part of Microsoft Visual Studio compiler support
>  * Process, pipeline, and download area for signed builds of kernel-mode drivers
>      - virt2phys security hardening
>  
> 






  parent reply	other threads:[~2023-08-12 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 19:13 Tyler Retzlaff
2023-03-08  0:08 ` Tyler Retzlaff
2023-08-12 14:10 ` Thomas Monjalon [this message]
2023-08-16 22:27   ` Tyler Retzlaff
2023-08-16 22:23 ` [PATCH v2] " Tyler Retzlaff
2023-08-15 15:43 [PATCH] " 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=2568979.Lt9SDvczpP@thomas \
    --to=thomas@monjalon.net \
    --cc=roretzla@linux.microsoft.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).