From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com [209.85.215.43]) by dpdk.org (Postfix) with ESMTP id 3BE2E1B246 for ; Tue, 31 Oct 2017 22:51:17 +0100 (CET) Received: by mail-lf0-f43.google.com with SMTP id g70so474546lfl.3 for ; Tue, 31 Oct 2017 14:51:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=xw2swUcUY1cddSM1jgCLcIL7nM5Gsnz/sHVq85h0Kyg=; b=ofSNDAl0pP6f3Q0BuED4oH91JA+BtIpHGqJuZrQFj7Bn127SRpenrG+V80GqT1m/EK 39euH62a+jpUhwxU3LeHb0268GFJaZuuKjeDZB/mneaqnE4HV8mIXolo/s5oh9D+1fIl +8fceyhkNOmWHfVf0Yd/qY3QtNU9Lr0rmvHJa6RdvrJdpfjBV6stG94/pMc7bLVOZQM3 Ich19OvPOIR8Sq7vqQM4DyJTqnhp0KveyBvmnolI/I7gcySxB6kSOfmWZL/qJhVBZsgh qi8pKjKmjsvlOUAO0QmksEfoYCb0cjRUiJWpc0Eee5DqwVD6LYjus9m3e32lBEapM410 eveQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=xw2swUcUY1cddSM1jgCLcIL7nM5Gsnz/sHVq85h0Kyg=; b=qfQbxjNTgmLtZnTcLWnsJ19DZVYH2EmXqa+yRD1yEsuraEiBzvB8kMziMbcL0Sx9jm 8yJkREPENX9uDoH3D8h/LV0luBKriHEc655K2VZOGDZGerGzO1BvpciUAYN9D8DsRsU9 y0aH58hPzb4hc70jozkuL/9jPAiZnwNxr8m1axNOh1bJu4ufwopVG1drwpah4HFMloxz rnxeSD0Gs14vC1flMtEeRotweCi5vgKAc9TbW/PI9kxI/4Cs7FBJQFzWU5SM+Aqkuo01 cRcuoJ86GJpVlFEAAcuypsjqDBpYqnOm0Z2BcDDr0DWKzrl3QhIr1lwpFRX+J/EzpTTZ Es/Q== X-Gm-Message-State: AMCzsaVto5K+nHS3J3TjGbfCRVqOkB+usCLq3PrDQ0kn2reSKeklGfHX 6zD0NjKa0w/WP6Z1j5fTcXxLEw== X-Google-Smtp-Source: ABhQp+RZrIqktN1n12TmIxSli4j1AGEvexqty+0Iv8yByjAKGPy3Mm/4JnMGq7abzQQiqnG338T66A== X-Received: by 10.46.89.199 with SMTP id g68mr1631792ljf.12.1509486676648; Tue, 31 Oct 2017 14:51:16 -0700 (PDT) Received: from shemminger-XPS-13-9360 (static-92-33-18-3.sme.bredbandsbolaget.se. [92.33.18.3]) by smtp.gmail.com with ESMTPSA id k184sm410620lfg.47.2017.10.31.14.51.16 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 31 Oct 2017 14:51:16 -0700 (PDT) Date: Tue, 31 Oct 2017 22:50:48 +0100 From: Stephen Hemminger To: James Bensley Cc: users@dpdk.org Message-ID: <20171031225048.34120581@shemminger-XPS-13-9360> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-users] DPDK support for 82579 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Oct 2017 21:51:17 -0000 On Tue, 31 Oct 2017 12:14:16 +0000 James Bensley wrote: > Hi All, >=20 > I have see the list of support NICs here: http://dpdk.org/doc/nics >=20 > Although it doesn=E2=80=99t say which NICs are confirmed as NOT working. I > have looking into DPDK support (for Pktgen and Moongen) on commodity > devices (e.g. laptops and desktops). I have DPDK + Pktgen compiled and > working on my home desktop: >=20 > bensley@htpc-ubuntu:/opt/dpdk/dpdk-17.08/usertools$ lspci | grep Eth > 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection > I217-V (rev 05) >=20 > However on my laptop it seems the NIC is =E2=80=9Cunsupported=E2=80=9D: >=20 > bensley@ubuntu-laptop:/opt/dpdk/dpdk-17.08/usertools$ lspci | grep Eth > 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network > Connection (rev 04) >=20 > When I say unsupported I mean that Intel 82579 chips aren=E2=80=99t on the > list of supported NICs (where as I217 is explicitly listed) so I have > two questions; >=20 > 1. Is there a list of confirmed unsupported NICs? >=20 > 2. It maybe that this NIC will work but it is untested (unless someone > can confirm otherwise) so is there a way I can force DPDK + Pktgen to > try and use this 82579 NIC? >=20 > Please see this output of me trying to bind the laptop NIC to DPDK, > dpdk-devbind.py doesn't explicitly reject the NIC (by which I mean no > error message and the return code from `sudo ./dpdk-devbind.py -b > e1000e 00:19.0` is 0) but it simply doesn=E2=80=99t work, the NIC is =E2= =80=9Cgiven=E2=80=9D > back to the Kernel: > https://null.53bits.co.uk/uploads/linux/applications/dpdk/Ubuntu-Laptop-D= PDK-NIC-Bind.txt >=20 > In the `lshw` output it can be seen that the NIC uses an e1000e > driver, do I need to compile the e1000e driver bundled with the DPDK > source and replace my existing/native driver with that, if so how can > I compile it? >=20 > bensley@ubuntu-laptop:/opt/dpdk/dpdk-17.08/drivers/net/e1000$ make > Makefile:32: /mk/rte.vars.mk: No such file or directory > Makefile:103: /mk/rte.lib.mk: No such file or directory > make: *** No rule to make target '/mk/rte.lib.mk'. Stop. >=20 > Cheers, > James. >=20 > P.S. I=E2=80=99m using DPDK 17.08 and Pktgen 3.4.2, I did a vanilla compi= le, > using these exact commands: > https://null.53bits.co.uk/index.php?page=3Dptkgen-install First off, I assume the device works for normal Linux networking. Then check the PCI-id value for the device and see if it is present in driv= ers/net/e1000 in DPDK. If not, then it maybe as simple as adding the necessary ID value t= o the table. Also, check current git.=20 It maybe more complex where some PHY code has to be backported from BSD into DPDK. Unfortunately, the device support in DPDK lags behind Linux and BSD. There are many variants and even Intel doesn't have resources to keep DPDK up to all the current PCI id values.