From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: checklist for DPDK on Windows
Date: Tue, 19 Mar 2019 10:52:15 +0100
Message-ID: <5042183.hYBaOkdThe@xps>
References: <8738827.r4ctrtuu5E@xps>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: harini.ramakrishnan@microsoft.com, ocardona@microsoft.com,
 anand.rawat@intel.com, pallavi.kadam@intel.com, ranjit.menon@intel.com,
 jeffrey.b.shaw@intel.com, bruce.richardson@intel.com,
 stephen@networkplumber.org, jerin.jacob@caviumnetworks.com,
 rasland@mellanox.com
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
 [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 351CF4C94
 for <dev@dpdk.org>; Tue, 19 Mar 2019 10:52:20 +0100 (CET)
In-Reply-To: <8738827.r4ctrtuu5E@xps>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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
> usertools/dpdk-devbind.py
> drivers/bus/vdev
> drivers/bus/pci
> lib/librte_pci
> lib/librte_cmdline
> lib/librte_kvargs
> lib/librte_ring
> lib/librte_mempool
> lib/librte_mbuf
> lib/librte_net
> 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
> lib/librte_eal/windows/eal/eal.c
>     eal_create_runtime_dir()
>     rte_eal_iopl_init()
> lib/librte_eal/windows/eal/eal_alarm.c
> lib/librte_eal/windows/eal/eal_cpuflags.c
> lib/librte_eal/windows/eal/eal_debug.c
> lib/librte_eal/windows/eal/eal_dev.c
> lib/librte_eal/windows/eal/eal_interrupts.c
> lib/librte_eal/windows/eal/eal_lcore.c
> lib/librte_eal/windows/eal/eal_log.c
> lib/librte_eal/windows/eal/eal_memory.c
> lib/librte_eal/windows/eal/eal_thread.c
> lib/librte_eal/windows/eal/eal_timer.c
> 
> 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.