From: Thomas Monjalon <thomas@monjalon.net>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: web@dpdk.org, Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>
Subject: Re: [dpdk-web] [PATCH] update Windows roadmap
Date: Fri, 10 Sep 2021 17:42:16 +0200 [thread overview]
Message-ID: <2221611.IfIjfMCkMc@thomas> (raw)
In-Reply-To: <20210827002727.113426-1-dmitry.kozliuk@gmail.com>
27/08/2021 02:27, Dmitry Kozlyuk:
> 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>
> ---
[...]
> +Upstream supports running testpmd and examples
It's strange to talk about "Upstream" on the upstream website.
Better to give a version number.
> +with mlx5, i40e, ice, vmxnet3 HW, or with PCAP virtual device.
What is vmxnet3 HW?
> +It requires yet unsigned kernel-mode drivers to run (except mlx5).
> +Only network some PMDs are currently enabled.
Syntax typo in above syntence.
> +
> +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.
[...]
> +* 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
I don't understand what it means.
> +* Process, pipeline, and download area for signed builds of kernel-mode drivers
> + - virt2phys security hardening
> +#### Feature Support
>
> +* Interrupt handling for netuio
> +* Fix for vmxnet3 PMD with VMWare hypervisor
A fix is not a feature, why listing?
> +* virtio PMD
> +* ena PMD
> +* mlx5 PMD rte_flow features
> +* Unit-tests
> +* Tracing
> +* Documentation build (doxygen + sphinx)
>
> +#### Miscellaneous
>
> +* 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)
Reference to the workaround?
> +* Functional tests in CI
>
> +#### Future (unscheduled) {#future}
>
> +- Advanced memory management: IOMMU, inbox kernel-mode driver
> - Broadcom bnxt PMD
> - Chelsio cxgbe PMD
> - Cisco enic PMD
> - Marvell qede PMD
Those PMDs are referenced here since the beginning based of promises.
I think there is nothing concrete, not even a single announcement,
so it is better to remove.
next prev parent reply other threads:[~2021-09-10 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 0:27 Dmitry Kozlyuk
2021-09-10 15:42 ` Thomas Monjalon [this message]
-- 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=2221611.IfIjfMCkMc@thomas \
--to=thomas@monjalon.net \
--cc=Harini.Ramakrishnan@microsoft.com \
--cc=dmitry.kozliuk@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).