From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id BCDD7A0C41; Fri, 8 Oct 2021 08:54:46 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A006340685; Fri, 8 Oct 2021 08:54:46 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id B73314067E for ; Fri, 8 Oct 2021 08:54:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1633676085; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=73ndImk5nS+ZKeBRA6FW63aauKa3fbQCPLKgoh+2QPI=; b=OOFL3EQ9aF6Dakg4S27qFq56jMCnYovcUOzUOZA+cLVdp+hqWjMjTF5anJMM5vAmIcXkTN AHNhkbh3rvlRtg8H2BuwcBPDywQBECCHIGB0vRFYVBdECWEKOHsHlFBbh4VlWrDn3CVTdb GEnYQWo0r53oSsAZf50LSyz7jBYRIEw= Received: from mail-lf1-f70.google.com (mail-lf1-f70.google.com [209.85.167.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-559-I9VndNJdPGesyacdFJ_hwA-1; Fri, 08 Oct 2021 02:54:42 -0400 X-MC-Unique: I9VndNJdPGesyacdFJ_hwA-1 Received: by mail-lf1-f70.google.com with SMTP id i40-20020a0565123e2800b003f53da59009so6355996lfv.16 for ; Thu, 07 Oct 2021 23:54:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=73ndImk5nS+ZKeBRA6FW63aauKa3fbQCPLKgoh+2QPI=; b=QFjLvUoyeQ9xSwD3f3uwnZyy06APq4Z7bBPIUrxi83P/resj7dT/iEpiG8WuZYraqJ FV4vBJ+2JI7a5TdLMOPTI60elo/HnNJFOJqwfXlUGyYGfNj+rBrd7xe9+34FrH4ANs6x GnqCgy3pwpMuj867ymJeR3vJf7yy8peTqj6AeE+KZ9MnKmpk+z5/XWFAv3ezxW+u1cBD P0LaYYMpzKtJBFhE7mEP6IwPDEgSxrDZIb3AbvKm/yb4TvHJ/Yrw0k7oqSwOK6eipfmy P7sIcfGQswWky6HShcWjjVhjjGuIu1f7sMNyawrz0+bCxaDBeyFQRp9N+/kYqdY6zDT8 rLIA== X-Gm-Message-State: AOAM533+2GHZvLYkvRbdzCPKwIUo11M3zLnedO/Ng7wgdlht8yC5pmaF pj2JuDdKKX9bS7A/KXFkjjDfUiEWLvb/W+kTvpOZafkxRowSuH0l9/SzKhAzrRkJHxDMOopWevV iUDEx3kxsrZmnWaofzZw= X-Received: by 2002:ac2:4e0d:: with SMTP id e13mr8324215lfr.560.1633676080786; Thu, 07 Oct 2021 23:54:40 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxR1wE6Gm6zUtmdcCVrIXQrfONDzmTxjG5jDhlnkQoPc5Wt8RvlOJc8DKdawlzWmT1pUOR8UrnZzJYnG5pk9k8= X-Received: by 2002:ac2:4e0d:: with SMTP id e13mr8324202lfr.560.1633676080600; Thu, 07 Oct 2021 23:54:40 -0700 (PDT) MIME-Version: 1.0 References: <20211007202451.90271-1-u9012063@gmail.com> In-Reply-To: <20211007202451.90271-1-u9012063@gmail.com> From: David Marchand Date: Fri, 8 Oct 2021 08:54:29 +0200 Message-ID: To: William Tu Cc: dev , Dmitry Kozlyuk , Pallavi Kadam Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH] net/e1000: build on Windows X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Oct 7, 2021 at 10:25 PM William Tu 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 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 > --- > 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. Could you enable debug logs? It will be verbose but let's try with --log-level=*:debug. > testpmd: create a new mbuf pool : n=171456, size=2176, socket=0 > testpmd: preferred mempool ops selected: ring_mp_mc > > Warning! port-topology=paired and odd forward ports number, the last port will p > air with itself. > Configuring Port 0 (socket 0) > Port 0: 00:50:56:3A:4D:A6 > Checking link statuses... > Done > No commandline core given, start packet forwarding > allocation mode: native > Logical Core 1 (socket 0) forwards packets on 1 streams: > RX P=0/Q=0 (socket 0) -> TX P=0/Q=0 (socket 0) peer=02:00:00:00:00:00 > > io packet forwarding packets/burst=32 > nb forwarding cores=1 - nb forwarding ports=1 > port 0: RX queue number: 1 Tx queue number: 1 > Rx offloads=0x0 Tx offloads=0x0 > RX queue: 0 > RX desc=256 - RX free threshold=0 > TX desc=256 - TX free threshold=32 > TX offloads=0x0 - TX RS bit threshold=32 -- David Marchand