Re: [dpdk-dev] Windows Support Plan

> The main reason DPDK memory management works the way it does is because > of need to support multiprocess. In order to map memory in all > processes, we need that space reserved (otherwise there's no guarantee > that the newly mapped memory segment will be mapped in all processes, > and it'll

[dpdk-dev] [PATCH v3] net/i40e: relaxed barrier in the tx fastpath

To keep ordering of mixed accesses, rte_cio is sufficient. The rte_io barrier is overkill.[1] [1] http://inbox.dpdk.org/dev/CALBAE1M-ezVWCjqCZDBw+MMDEC4O9 qf0kpn89emdgdajepk...@mail.gmail.com Signed-off-by: Gavin Hu --- V3: - optimize the barriers in the fast path only, leave as it is for the

[dpdk-dev] Windows Draft Build

Hi, I'm having trouble building "dpdk.sln" from "windpdk-v18.08-clang" branch of "dpdk-draft-windows" repository using Visual Studio 2019 Community Edition. All projects are set up to use some "llvm" toolset. If I install LLVM Build Tools and switch toolset to Clang-cl, build fails because Platfor