Re: [dpdk-dev] [PATCH] net/e1000: build on Windows

[William Tu <u9012063@gmail.com>]

On Thu, Oct 7, 2021 at 11:54 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Thu, Oct 7, 2021 at 10:25 PM William Tu <u9012063@gmail.com> wrote:
> >
> > This patch enables building the e1000 driver for Windows.
> > I tested using two Windows VM on top of VMware Fusion,
> > creating two e1000 devices with device ID 0x10D3,
> > verifying rx/tx works correctly using dpdk-testpmd.exe
> > rxonly and txonly mode.
> >
> > Signed-off-by: William Tu <u9012063@gmail.com>
>
> Please, Cc: driver maintainers when touching one.
> You can pass --to-cmd or --cc-cmd ./devtools/get-maintainer.sh when
> calling git send-email as suggested in the contributing howto.
> https://doc.dpdk.org/guides/contributing/patches.html#sending-patches

Got it, thanks.

>
>
> > ---
> > Example when running:
> > PS C:\dpdk> .\build\app\dpdk-testpmd.exe
> > EAL: Detected CPU lcores: 4
> > EAL: Detected NUMA nodes: 1
> > EAL: Multi-process support is requested, but not available.
> > EAL: WARNING: TSC frequency estimated roughly - clock timings may be less accurate.
> > EAL: Probe PCI driver: net_e1000_em (8086:10d3) device: 0000:03:00.0 (socket 0)
> > EAL: Requested device 0000:1b:00.0 cannot be used
>
> Odd to read this, and still see testpmd getting one port afterwards.
This is expected. Because I only enable 1 dpdk port (0000:03:00.0)
The 0000:1b:00.0 is still running kernel driver. I will mention it in next
version.

Thanks
William