From: Thomas Monjalon <thomas@monjalon.net>
To: Omar Cardona <ocardona@microsoft.com>,
Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>
Cc: dev@dpdk.org, Olga Shern <olgas@mellanox.com>,
Ranjit Menon <ranjit.menon@intel.com>,
"pallavi.kadam@intel.com" <pallavi.kadam@intel.com>,
"jeffrey.b.shaw@intel.com" <jeffrey.b.shaw@intel.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
Raslan Darawsheh <rasland@mellanox.com>,
Khoa To <khot@microsoft.com>,
Eilon Greenstein <eilong@mellanox.com>,
cathal.ohare@intel.com, adham@mellanox.com, yohadt@mellanox.com,
talshn@mellanox.com, anans@mellanox.com,
jeffrey.tippet@microsoft.com, khot@microsoft.com,
nareshkumar.pbs@broadcom.com, Haseeb.Gani@cavium.com,
shshaikh@marvell.com
Subject: Re: [dpdk-dev] checklist for DPDK on Windows
Date: Tue, 28 May 2019 15:24:17 +0200 [thread overview]
Message-ID: <4849706.GfOQK6XAG1@xps> (raw)
In-Reply-To: <VI1PR05MB457497E3E43E60E1126EB081D3410@VI1PR05MB4574.eurprd05.prod.outlook.com>
Should we have a page with an up-to-date status of the work?
Would be good to have an overview of the progress,
even if it's not as simple as a progress bar :)
> From: Ranjit Menon <ranjit.menon@intel.com>
> > 15/03/2019 00:04, Thomas Monjalon:
> >> Hi,
> >>
> >> Below is a list of directories, files or functions which we need to
> >> check to make basic DPDK works on Windows.
> >> If something is missing, please complete.
> >>
> >> The goal of this list is to make a status of what is already done,
> >> and plan what should be done next. It will help to share the workload
> >> among all volunteers during the next months.
> >>
> >> buildtools/pmdinfogen
> - not ported to Windows
> >> usertools/dpdk-devbind.py
> - not ported to Windows
> >> drivers/bus/vdev
> - not ported to Windows
> >> drivers/bus/pci
> - ported to Windows in draft repo (using ICC)
> >> lib/librte_pci
> - ported to Windows in draft repo (using ICC)
> >> lib/librte_cmdline
> - ported to Windows in draft repo (using ICC)
> >> lib/librte_kvargs
> - ported to Windows in draft repo (using ICC)
> >> lib/librte_ring
> - ported to Windows in draft repo (using ICC)
> >> lib/librte_mempool
> - ported to Windows in draft repo (using ICC)
> >> lib/librte_mbuf
> - ported to Windows in draft repo (using ICC)
> >> lib/librte_net
> - ported to Windows in draft repo (using ICC)
> >> lib/librte_eal/common/include/rte_errno.h
> >> lib/librte_eal/common/include/rte_string_fns.h
> >> lib/librte_eal/common/include/rte_lcore.h
> >> lib/librte_eal/common/arch/x86/rte_cpuflags.c
> >> lib/librte_eal/common/arch/x86/rte_cycles.c
> >> lib/librte_eal/common/eal_common_options.c
> >> lib/librte_eal/common/eal_common_thread.c
> >> lib/librte_eal/common/eal_common_proc.c
> - most 'common' [c/h] files ported to Windows in draft repo (using ICC)
> >> lib/librte_eal/windows/eal/eal.c
> >> eal_create_runtime_dir()
> >> rte_eal_iopl_init()
> - part of file port available in "Helloworld" patch
> >> lib/librte_eal/windows/eal/eal_alarm.c
> - ported to Windows in draft repo (using ICC)
> >> lib/librte_eal/windows/eal/eal_cpuflags.c
> - not ported to Windows
> >> lib/librte_eal/windows/eal/eal_debug.c
> - part of file port available in "Helloworld" patch
> >> lib/librte_eal/windows/eal/eal_dev.c
> - not ported to Windows
> >> lib/librte_eal/windows/eal/eal_interrupts.c
> - ported to Windows in draft repo (using ICC)
> >> lib/librte_eal/windows/eal/eal_lcore.c
> - part of file port available in "Helloworld" patch
> >> lib/librte_eal/windows/eal/eal_log.c
> - ported to Windows in draft repo (using ICC)
> >> lib/librte_eal/windows/eal/eal_memory.c
> - ported to Windows in draft repo (using ICC)
> >> lib/librte_eal/windows/eal/eal_thread.c
> - part of file port available in "Helloworld" patch
> >> lib/librte_eal/windows/eal/eal_timer.c
> - ported to Windows in draft repo (using ICC)
> >>
> >> Please check this list and mention what is done or in progress.
> >> The best would be to reference some patches or commits to help
> >> progress together as a community, thanks.
prev parent reply other threads:[~2019-05-28 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 23:04 Thomas Monjalon
2019-03-14 23:04 ` Thomas Monjalon
2019-03-19 9:52 ` Thomas Monjalon
2019-03-19 9:52 ` Thomas Monjalon
2019-03-19 19:33 ` Ranjit Menon
2019-03-19 19:33 ` Ranjit Menon
2019-03-19 20:36 ` Omar Cardona
2019-03-19 20:36 ` Omar Cardona
2019-03-20 11:31 ` Olga Shern
2019-03-20 11:31 ` Olga Shern
2019-05-28 13:24 ` Thomas Monjalon [this message]
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=4849706.GfOQK6XAG1@xps \
--to=thomas@monjalon.net \
--cc=Harini.Ramakrishnan@microsoft.com \
--cc=Haseeb.Gani@cavium.com \
--cc=adham@mellanox.com \
--cc=anans@mellanox.com \
--cc=bruce.richardson@intel.com \
--cc=cathal.ohare@intel.com \
--cc=dev@dpdk.org \
--cc=eilong@mellanox.com \
--cc=jeffrey.b.shaw@intel.com \
--cc=jeffrey.tippet@microsoft.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=khot@microsoft.com \
--cc=nareshkumar.pbs@broadcom.com \
--cc=ocardona@microsoft.com \
--cc=olgas@mellanox.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=rasland@mellanox.com \
--cc=shshaikh@marvell.com \
--cc=stephen@networkplumber.org \
--cc=talshn@mellanox.com \
--cc=yohadt@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).