From: William Tu <u9012063@gmail.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK 21.11+ Windows Roadmap
Date: Thu, 26 Aug 2021 19:31:05 -0700 [thread overview]
Message-ID: <CALDO+SawKOrrqQX9On=-Pun808G4HEbppcu3Q+wTCKTDWk7-WA@mail.gmail.com> (raw)
In-Reply-To: <20210827031853.214ca205@sovereign>
Hi Dmitry,
Thanks, I have one question.
On Thu, Aug 26, 2021 at 5:19 PM Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> wrote:
>
> This roadmap has been discussed on Windows community calls Aug 5 and Aug 19
> and it met no principal objections. It extends beyond the nearest release,
> but it is useful to have a comprehensive backlog in one place.
>
> In 21.11 it looks realistic to have:
>
[...]
> 4. Miscellaneous
>
> 4.1. Refactor bus/pci (DmitryK)
>
> Currently netuio maps BARs at PCI bus scan. This is against DPDK model
> and can break certain scenarios, like running apps with different sets of
> available PMDs. PCI bus driver code must be refactored.
Can you elaborate more about the "against DPDK model" and the
scenarios it might break?
I thought it's common that when a driver loads, it scans PCI configuration
space, and mmap BARs. So I'm curious why it's an issue for DPDK.
>
> 4.2. Move from Setup API to cfgmgr32 API in EAL and bus/pci (DmitryK)
>
> Setup API is deprecated, also Tyler indicated it causes layering
> violation warnings by Microsoft internal tools. To make DPDK a good
> Windows citizen, cfgmgr32 should be used to work with devices and driver
> interfaces.
>
> 4.3. Enable unit tests [unit] (Jie Zhou)
>
> 4.5. Add WPP(?) tracing to netuio
>
> Debugging netuio loading issues in VMWare case appeared to be impossible
> until adding debug prints to pinpoint the place of failure. Tracing all
> errors at least would help. virt2phys is also getting tracing in the
> recent patch series. End-users can collect traces and attach them to
> bug reports, this should be added to DPDK user documentation.
> It is unclear who will do this and when, but Microsoft approves the
> idea and can provide guidance on tracing technologies.
>
> 4.6. Find a way to install netuio without GUI.
>
> Currently in requires Device Manager GUI, which is absent in WS Core,
> it is also inconvenient to lack commands for copy&paste.
> Investigate [devmgr].
I'd love to have this. It's pretty inconvenient using GUI.
Thanks!
William
next prev parent reply other threads:[~2021-08-27 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 0:18 Dmitry Kozlyuk
2021-08-27 2:31 ` William Tu [this message]
2021-08-27 21:41 ` Dmitry Kozlyuk
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='CALDO+SawKOrrqQX9On=-Pun808G4HEbppcu3Q+wTCKTDWk7-WA@mail.gmail.com' \
--to=u9012063@gmail.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
/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).