From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f53.google.com (mail-pl0-f53.google.com [209.85.160.53]) by dpdk.org (Postfix) with ESMTP id 9FDFC1D7 for ; Tue, 2 Jan 2018 05:27:36 +0100 (CET) Received: by mail-pl0-f53.google.com with SMTP id g2so27949431pli.8 for ; Mon, 01 Jan 2018 20:27:36 -0800 (PST) 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=2XrLQLinHdqB0BYdhIRVxxnQ06ZjzwNLE2WmVUV7yT8=; b=GMP3lBkkbMckba7/YbHmRDqKdN8JLBMgTVIz/gFzRr7xlqznU2RkLIbzkmNMwPzlo4 FJVSCIeNumxwEgir1w5APtoJzKMCs9Sj6Vdlyk4g0vJ5z3obQjBNd5w0YvUTRbxhEI7c o8YsVYDm9eQe37YWVK+BE3qaoJePQTD9GjK0isSWXPmFiICz0Z7XIJv3/sbv7lb8AL/f FR10o/4CB042/SJ9px6RLxlZO8N55gTNpfhmKhGxoOhO0jhtp41+W4eZyiCRxf2hiNKv cJUbV45Dy8VzwBgwl7Dq/RZHe7kltY0MvAtW5u9QGK6m5YPuZg02hnk65Y71X5v1eUnv iKHA== 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=2XrLQLinHdqB0BYdhIRVxxnQ06ZjzwNLE2WmVUV7yT8=; b=V3k9rFckrqqHMLs9tyh/RRBfbuvBGMPzNJIa8IgnapceyZP1i9qp/2aSpjyBPYWASB 8FpF9Sdk+dzaFfFiIvebD42B+x119yUvb6ZbAkXr/tiNuNqjwNA10Ewkq8sZRB4z/RJa Jr+4CEOUxfS/iP3GeOpRSBFpLx4tpdHkj4NpXtvXvvm0qml4lvzqBT6QjvQPJ3CSiwcG 7Nr9jdbMdxlywamPbwOEK0Ju+OcVsh8wKi4U+x6iMaIOrBqfSecXvlA/SvsG9JKA73oQ ExBzPcdLuFnmz9JwbL//+PODKKJ5sDishhktkSETNtZ+tkonXODHKDqCZV6+m2QHlGFk 373Q== X-Gm-Message-State: AKGB3mKW0++cz+BpzV754xpRaLeeMmLPWHWtaWN6zAb1JLnoCMEWaNLX q9rFvBlyXZMY7SUKCiSL766ITE2vk3E= X-Google-Smtp-Source: ACJfBotI9GE2APj+AkVboFo50Yoha4dEoZw8sleG1TejutPneNv0ZUbOQVRF58EZz2HBZYpSB868Aw== X-Received: by 10.84.195.36 with SMTP id i33mr45131719pld.189.1514867255619; Mon, 01 Jan 2018 20:27:35 -0800 (PST) Received: from xeon-e3 (204-195-18-133.wavecable.com. [204.195.18.133]) by smtp.gmail.com with ESMTPSA id n65sm89109410pfa.83.2018.01.01.20.27.34 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 01 Jan 2018 20:27:35 -0800 (PST) Date: Mon, 1 Jan 2018 20:27:32 -0800 From: Stephen Hemminger To: Hui Ling Cc: Andrew Bainbridge , "users@dpdk.org" Message-ID: <20180101202732.6423d6b9@xeon-e3> In-Reply-To: References: <2151087.Q62u2efIDs@xps> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] DPDK mlx4 PMD on Azure VM 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, 02 Jan 2018 04:27:36 -0000 On Thu, 21 Dec 2017 15:35:00 +0800 Hui Ling wrote: > Andy, > > My last VM is not in "Canada East" center since no AN type of instance > was available to me at the time I created my VM. > > Just tried on a same type VM in Canada East, and it seems that the > location does make a difference. > > This time, I was able to run testpmd without any explicit errors: > > root@myVM:/home/hling/dpdk-17.11# build/app/testpmd -l 1-2 -n 4 -w > 0004:00:02.0 0002:00:02.0 -- --rxq=2 --txq=2 -i > EAL: Detected 4 lcore(s) > EAL: No free hugepages reported in hugepages-1048576kB > EAL: Probing VFIO support... > EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using > unreliable clock cycles ! > EAL: PCI device 0004:00:02.0 on NUMA socket 0 > EAL: probe driver: 15b3:1004 net_mlx4 > PMD: mlx4.c:465: mlx4_pci_probe(): PCI information matches, using > device "mlx4_3" (VF: true) > PMD: mlx4.c:492: mlx4_pci_probe(): 1 port(s) detected > PMD: mlx4.c:586: mlx4_pci_probe(): port 1 MAC address is 00:0d:3a:f4:49:c4 > Interactive-mode selected > USER1: create a new mbuf pool : n=155456, > size=2176, socket=0 > Configuring Port 0 (socket 0) > Port 0: 00:0D:3A:F4:49:C4 > Checking link statuses... > Done > > testpmd> start tx_first > io packet forwarding - ports=1 - cores=1 - streams=2 - NUMA support > enabled, MP over anonymous pages disabled > Logical Core 2 (socket 0) forwards packets on 2 streams: > RX P=0/Q=0 (socket 0) -> TX P=0/Q=0 (socket 0) peer=02:00:00:00:00:00 > RX P=0/Q=1 (socket 0) -> TX P=0/Q=1 (socket 0) peer=02:00:00:00:00:00 > > io packet forwarding - CRC stripping enabled - packets/burst=32 > nb forwarding cores=1 - nb forwarding ports=1 > RX queues=2 - RX desc=128 - RX free threshold=0 > RX threshold registers: pthresh=0 hthresh=0 wthresh=0 > TX queues=2 - TX desc=512 - TX free threshold=0 > TX threshold registers: pthresh=0 hthresh=0 wthresh=0 > TX RS bit threshold=0 - TXQ flags=0x0 > testpmd> stop > Telling cores to stop... > Waiting for lcores to finish... > > ------- Forward Stats for RX Port= 0/Queue= 0 -> TX Port= 0/Queue= 0 ------- > RX-packets: 0 TX-packets: 32 TX-dropped: 0 > ------- Forward Stats for RX Port= 0/Queue= 1 -> TX Port= 0/Queue= 1 ------- > RX-packets: 0 TX-packets: 32 TX-dropped: 0 > ---------------------- Forward statistics for port 0 ---------------------- > RX-packets: 0 RX-dropped: 0 RX-total: 0 > TX-packets: 64 TX-dropped: 0 TX-total: 64 > ---------------------------------------------------------------------------- > > +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++ > RX-packets: 0 RX-dropped: 0 RX-total: 0 > TX-packets: 64 TX-dropped: 0 TX-total: 64 > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Done. > testpmd> > > > > Not sure why I don't see any packets transmission, but at least the > MLX4 PMD seems to be able to talk to the mlx4_en driver, or is it? > > Will keep digging. > > Hui > > On Wed, Dec 20, 2017 at 9:39 PM, Andrew Bainbridge > wrote: > > Hi Hui > > > > Did you create your VM in the "Canada East" data center? This page suggests that is a requirement: > > https://azure.microsoft.com/en-us/blog/azure-networking-updates-for-fall-2017/ > > > > Also, I seem to remember reading that the VM must have at least 8 cores. Sorry, I can't find a reference for that. > > > > - Andy > > > > -----Original Message----- > > From: Hui Ling > > > > This is my VM info in case it is needed. > > ======================================================================================================= > > A Standard_DS3_v2 instance from Azure. (one of these models support AN) > > You will need to a couple of things. 1. Make sure you have a VM capable of accelerated networking, and that your Azure account has opt-ed in. Last I checked it was still in preview until RHEL 7 with AN support was released. https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-create-vm-accelerated-networking There are many different regions, and most have AN by now. Which one are you trying? Make sure Linux without DPDK is working with AN first. 2. DPDK support requires 17.11 or later DPDK and the failsafe and TAP PMD's. The Mellanox mlx4 on Azure is only used after a flow is established. The initial packet (and broadcast/multicast) show up on the non-accelerated netvsc device. See the DPDK User Summit in Dublin 2017 for more detal. For later releases if you watch the development mailing list you will see the enhancements being done to simplify setup of TAP/failsafe.