Re: [dpdk-dev] DPDK Windows Build

2020-01-28 Thread Dmitry Kozliuk
Hello Jeremy, > clang: error: no such file or directory: '/OPT:REF' There is a bug in Meson: '/OPT:REF' must be prefixed with '-Wl,' when using Clang with link.exe, because Clang does not recognize '/OPT:REF' as an argument to pass to linker, but treats it as a filename instead. A patch is not un

Re: [dpdk-dev] [PATCH v6 03/10] eal: include filesystem implementation for windows

2020-01-30 Thread Dmitry Kozliuk
Hello Pallavi, > +#include "eal_internal_cfg.h" > + > +/* sets up platform-specific runtime data dir */ > +int > +eal_create_runtime_dir(void); > + > +/* returns runtime dir */ > +const char * > +eal_get_runtime_dir(void); Any reason not to #include "eal_filesystem.h"? > + > +static inline const

Re: [dpdk-dev] DPDK Windows Build

2020-02-01 Thread Dmitry Kozliuk
Hi William, > Sanity check compile stderr: > clang.exe: error: linker command failed with exit code 1104 (use -v to > see invocation) Please add '-v' flag to Meson invocation and post the output as plain text. The exact commands you're using will also help. > Program cat found: YES (C:\MinGW\msy

[dpdk-dev] Windows Support Plan

2020-02-02 Thread Dmitry Kozliuk
Hi everyone! Where do I find a high-level plan of comprehensive Windows support: design decisions, implementation order, etc? Information on the subject is very scarce, one may think it is abandoned. Googling for "site:dpdk.org/ml/archives/dev/ windows" yields only two pages of disjoint messages.

Re: [dpdk-dev] DPDK Windows Build

2020-02-03 Thread Dmitry Kozliuk
> > Do I mess up some linker's configurations? > I attached the meson log, thanks for your help! Those are not errors, just harmless warnings. You can now build and run an example program (rerun meson with -Dexamples=helloworld per Windows Getting Started Guide).

Re: [dpdk-dev] [PATCH v2 0/7] MinGW-w64 support

2020-02-07 Thread Dmitry Kozliuk
Hi William, I applied your v2 patch and I did a native build on windows 10. > Hit an error showing > ../lib/librte_eal/windows/eal/eal_lcore.c:54:2: error: 'for' loop > initial declarations are only allowed in C99 mode > Thanks, will fix in v3. However the output looks weird: > C:\dpdk\build\exa

Re: [dpdk-dev] [PATCH v8 03/11] eal: introduce memory management wrappers

2020-06-12 Thread Dmitry Kozliuk
> [...] > > +INTERNAL { > > + global: > > + > > + rte_mem_lock; > > + rte_mem_map; > > + rte_mem_page_size; > > + rte_mem_unmap; > > +}; > > Not sure why these functions are internal. > They may be useful for DPDK applications. > We would need to add the file in doxygen index. >

Re: [dpdk-dev] [PATCH v8 03/11] eal: introduce memory management wrappers

2020-06-12 Thread Dmitry Kozliuk
> > > Not sure if they are in DPDK scope, apart from rte_mem_lock, which > > generalizes rte_mem_lock_page already in rte_memory.h. What may be > typical > > use cases for data-plane apps? I can see testpmd using mmap for > allocating > > external memory (because of possible use of hugepages), doe

Re: [dpdk-dev] [PATCH v4 25/27] eal: mark old naming as deprecated

2020-07-17 Thread Dmitry Kozliuk
On Fri, Jul 17, 2020, 18:21 Burakov, Anatoly wrote: > On 16-Jul-20 11:04 PM, Stephen Hemminger wrote: > > On Thu, 16 Jul 2020 14:41:41 +0100 > > "Burakov, Anatoly" wrote: > > > >> On 15-Jul-20 9:29 PM, Stephen Hemminger wrote: > >>> On Wed, 15 Jul 2020 14:28:17 +0100 > >>> "Burakov, Anatoly" wr