From: Thomas Monjalon <thomas@monjalon.net>
To: Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>
Cc: Omar Cardona <ocardona@microsoft.com>,
Dmitry Malloy <dmitrym@microsoft.com>,
Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
Pallavi Kadam <pallavi.kadam@intel.com>,
Ranjit Menon <ranjit.menon@intel.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Tal Shnaiderman <talshn@mellanox.com>,
Fady Bader <fady@mellanox.com>, Ophir Munk <ophirmu@mellanox.com>,
dev@dpdk.org
Subject: [dpdk-dev] Windows DPDK progress
Date: Mon, 06 Apr 2020 18:43:37 +0200 [thread overview]
Message-ID: <4220616.PpUMLH0tvb@xps> (raw)
The roadmap for DPDK support on Windows is updated on the website:
http://core.dpdk.org/roadmap/windows/
The last major step completed was:
- MinGW integration for GCC support on Windows
We are a bit late for these tasks:
- basic memory management
- other basic EAL routines
- PCI probing
- netuio hosting
Below are status and action items for current tasks.
1/ Memory Management
Dmitry Kozlyuk sent patches and wait for reviews:
http://inbox.dpdk.org/dev/20200330041026.784624-1-dmitry.kozliuk@gmail.com/
It was agreed during last meeting that Microsoft and Intel are
assigned to review these patches, preferably before last Saturday.
There were only few comments from Marvell and Mellanox so far.
2/ Other EAL Routines
Not clear what are the next EAL functions to be implemented for Windows.
Intel and Mellanox are supposed to work on EAL routines like logging
and CPU cycles.
I propose Intel completes the work on logging,
while Mellanox implements CPU cycles reading.
3/ PCI Probing
Mellanox is working on PCI probing, including PCI library and PCI bus.
The patches should be sent in few days.
Next step is for Intel to provides patches for specific steps needed
when probing PCI devices which are bound to netuio.
4/ netuio Hosting
It seems netuio is blocked in Microsoft because of legal issues.
Until netuio legal issues are fixed, only Mellanox PMD can
be supported. This is a red flag for the whole project.
A mitigation to help progress is to merge virt2phys driver from Dmitry:
http://inbox.dpdk.org/dev/20200330041026.784624-2-dmitry.kozliuk@gmail.com/
Waiting for virt2phys review from Intel.
Please update the status & plan if something is missing.
I will send some updates regularly, but please do not use this thread
for technical discussions.
You should be able to follow the status through this tool:
http://inbox.dpdk.org/dev/?q=s:Windows+s:progress
reply other threads:[~2020-04-06 16:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4220616.PpUMLH0tvb@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=fady@mellanox.com \
--cc=harini.ramakrishnan@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=ocardona@microsoft.com \
--cc=ophirmu@mellanox.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@mellanox.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).