DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, david.marchand@redhat.com
Subject: Microsoft DPDK 24.07 Release Roadmap
Date: Thu, 25 Apr 2024 13:50:16 -0700	[thread overview]
Message-ID: <20240425205016.GB9356@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)

Microsoft DPDK 24.07 Release Roadmap

1. Update drivers to use optional stdatomic macros

  Continuation of work started in 24.11 release.

  Use stdatomic API
  https://patchwork.dpdk.org/project/dpdk/list/?series=31797

2. MSVC Enable working Application & Nvidia mlx5 Driver

  Bring MSVC built libraries and drivers significantly closer
  to parity with LLVM/Windows builds.

  The set of series when merged allow the following libs
  to be built: log, kvargs, telemetry, eal, ring, rcu, mempool,
  mbuf, net, meter, ethdev, pci, cmdline, metrics, hash, timer,
  bitratestats, cfgfile, cryptodev, gpudev, gro, gso, ip_frag,
  latencystats, pcapng, rib, reorder, security

  The set of series when merged allow the following drivers
  to be built: bus/{auxiliary,pci,vdev}, mempool/ring,
  {common,net,crypto}/mlx5

  Remove use of VLAs
  https://patchwork.dpdk.org/project/dpdk/list/?series=31785

  Structure packing
  https://patchwork.dpdk.org/project/dpdk/list/?series=31751

  Use C standard flexible array member
  https://patchwork.dpdk.org/project/dpdk/list/?series=31404

  Remove RTE_MARKER
  https://patchwork.dpdk.org/project/dpdk/list/?series=31681

  Use only SSE/AVX SIMD (no MMX)
  https://patchwork.dpdk.org/project/dpdk/list/?series=31643

  Provide and use __rte_constant for MSVC
  https://patchwork.dpdk.org/project/dpdk/list/?series=31578

  Provide crc32 inline functions for MSVC
  https://patchwork.dpdk.org/project/dpdk/list/?series=31577

  Provide ffs{32,64} and movdiri for MSVC
  https://patchwork.dpdk.org/project/dpdk/list/?series=31576

  Adapt prefetch functions for MSVC
  https://patchwork.dpdk.org/project/dpdk/list/?series=31575

  Adapt {net/common}/mlx5 for MSVC
  <series not yet submitted>

3. Windows Build Static & Dynamic Linking

  Clean up and enable the first usable dll based DPDK.

  Build only static or dynamic DPDK
  https://patchwork.dpdk.org/project/dpdk/list/?series=31744

  Build libraries with MSVC by default
  https://patchwork.dpdk.org/project/dpdk/list/?series=31673

  Build drivers with MSVC by default
  <series not yet submitted>

  Initialize shared plugins on Windows/MSVC
  https://patchwork.dpdk.org/project/dpdk/list/?series=31482

  Correctly import/export data variables for Windows/MSVC
  <series not yet submitted>

4. MSVC Bugs / Other Bugs

  Bugs and warnings fixes to keep the CI for Windows clean.

  Fix missing type in dtor expansion
  https://patchwork.dpdk.org/project/dpdk/list/?series=31760

  Fix returning value from void return functions
  https://patchwork.dpdk.org/project/dpdk/list/?series=31448

  Fix use rte macros instead of __attribute
  https://patchwork.dpdk.org/project/dpdk/list/?series=31407

  Install sched.h header on Windows
  https://patchwork.dpdk.org/project/dpdk/list/?series=31486

  Warning cast away atomic qualification
  https://patchwork.dpdk.org/project/dpdk/list/?series=31759

  Warning unsigned / signed mismatch
  https://patchwork.dpdk.org/project/dpdk/list/?series=31748

  Warning double truncation
  https://patchwork.dpdk.org/project/dpdk/list/?series=31747


             reply	other threads:[~2024-04-25 20:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 20:50 Tyler Retzlaff [this message]
2024-04-25 23:04 ` Tyler Retzlaff

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=20240425205016.GB9356@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
    --to=roretzla@linux.microsoft.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --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).