From: Jason Messer <jmesser@microsoft.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Kappler, Elizabeth M" <elizabeth.m.kappler@intel.com>,
Omar Cardona <ocardona@microsoft.com>,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] Request to create a draft repo for Windows DPDK Patches
Date: Mon, 19 Feb 2018 18:02:46 +0000 [thread overview]
Message-ID: <DM5PR2101MB1014CE24B27B95CB3484CFF1B4C80@DM5PR2101MB1014.namprd21.prod.outlook.com> (raw)
In-Reply-To: <DM5PR2101MB10146A9C13BEA6E1CCF2AA7CB4CB0@DM5PR2101MB1014.namprd21.prod.outlook.com>
Resending on dev alias
-----Original Message-----
From: Jason Messer
Sent: Friday, February 16, 2018 10:52 AM
To: users@dpdk.org
Cc: Kappler, Elizabeth M <elizabeth.m.kappler@intel.com>; Omar Cardona <ocardona@microsoft.com>; techboard@dpdk.org
Subject: Request to create a draft repo for Windows DPDK Patches
Hello -
As we reported at the DPDK Summit in November, we have brought support for several of the DPDK core libraries as well as a UIO driver for use on Windows. While there is still work to do (outlined below) we are requesting a draft repo be created to continue this work more openly in the community and to provide a forum to address any technical concerns.
We expect the initial commit for this draft repo (branch tentatively named windpdk-v17.11-rc2) to include the following libraries.
- librte_bus_pci
- librte_cmdline
- librte_distributor
- librte_eal
- librte_ether
- librte_hash
- librte_kvargs
- librte_lpm
- librte_mbuf
- librte_mempool
- librte_mempool_ring
- librte_pci
- librte_pmd_i40e (Intel PMD for Fortville NICs)
- librte_ring
Additionally, these two toy applications are building and running correctly:
- l2fwd
- l3fwd
Note: code is currently based on v17.11 release but we plan to quickly rebase so that we are current with the latest 18.02 release and eventually in-sync with upstream.
Outstanding Issues:
- Confirm DPDK libraries and UIO driver build correctly with Clang on windows
- Update Visual Studio projects / solutions to reference clang compiler (currently expects ICC)
- [Tangential] Make DPDK C-Standards Compliant to not require specific GNU/GCC extensions
- Clean-up code and refactor to remove as many #ifdefs as possible
- Bring remaining DPDK core libraries to Windows and confirm
- Integrate with Meson build tool suite
Thanks,
Jason
next parent reply other threads:[~2018-02-19 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM5PR2101MB10146A9C13BEA6E1CCF2AA7CB4CB0@DM5PR2101MB1014.namprd21.prod.outlook.com>
2018-02-19 18:02 ` Jason Messer [this message]
2018-02-28 20:08 ` [dpdk-dev] [dpdk-announce] git repository for DPDK on Windows 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=DM5PR2101MB1014CE24B27B95CB3484CFF1B4C80@DM5PR2101MB1014.namprd21.prod.outlook.com \
--to=jmesser@microsoft.com \
--cc=dev@dpdk.org \
--cc=elizabeth.m.kappler@intel.com \
--cc=ocardona@microsoft.com \
--cc=techboard@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).