From: Thomas Monjalon <thomas@monjalon.net>
To: harini.ramakrishnan@microsoft.com
Cc: 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, dev@dpdk.org,
jerin.jacob@caviumnetworks.com, rasland@mellanox.com
Subject: [dpdk-dev] checklist for DPDK on Windows
Date: Fri, 15 Mar 2019 00:04:52 +0100 [thread overview]
Message-ID: <8738827.r4ctrtuu5E@xps> (raw)
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.
next reply other threads:[~2019-03-14 23:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 23:04 Thomas Monjalon [this message]
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
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=8738827.r4ctrtuu5E@xps \
--to=thomas@monjalon.net \
--cc=anand.rawat@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harini.ramakrishnan@microsoft.com \
--cc=jeffrey.b.shaw@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=ocardona@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=rasland@mellanox.com \
--cc=stephen@networkplumber.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).