[dpdk-dev] checklist for DPDK on Windows

Olga Shern olgas at mellanox.com
Wed Mar 20 12:31:28 CET 2019


+Eilon 

Thanks,
Olga

-----Original Message-----
From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Omar Cardona
Sent: Tuesday, March 19, 2019 10:36 PM
To: Ranjit Menon <ranjit.menon at intel.com>; Thomas Monjalon <thomas at monjalon.net>; dev at dpdk.org
Cc: Harini Ramakrishnan <Harini.Ramakrishnan at microsoft.com>; anand.rawat at intel.com; pallavi.kadam at intel.com; jeffrey.b.shaw at intel.com; bruce.richardson at intel.com; stephen at networkplumber.org; jerin.jacob at caviumnetworks.com; Raslan Darawsheh <rasland at mellanox.com>; Khoa To <khot at microsoft.com>
Subject: Re: [dpdk-dev] checklist for DPDK on Windows

+Khoa

-----Original Message-----
From: Ranjit Menon <ranjit.menon at intel.com>
Sent: Tuesday, March 19, 2019 12:34 PM
To: Thomas Monjalon <thomas at monjalon.net>; dev at dpdk.org
Cc: Harini Ramakrishnan <Harini.Ramakrishnan at microsoft.com>; Omar Cardona <ocardona at microsoft.com>; anand.rawat at intel.com; pallavi.kadam at intel.com; jeffrey.b.shaw at intel.com; bruce.richardson at intel.com; stephen at networkplumber.org; jerin.jacob at caviumnetworks.com; rasland at mellanox.com
Subject: Re: [dpdk-dev] checklist for DPDK on Windows

Thomas...
Status below:


On 3/19/2019 2:52 AM, Thomas Monjalon wrote:
> Any feedback?
> Could we try to give a work estimation for these items?
> 
> 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.
> 
> 
> 


More information about the dev mailing list