From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx03b-out01ag.rit.edu (mx03b-out01ag.rit.edu [129.21.3.135]) by dpdk.org (Postfix) with ESMTP id 54B722C55 for ; Tue, 12 Dec 2017 13:21:55 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rit.edu; i=@rit.edu; q=dns/txt; s=rit1608; t=1513081316; x=1544617316; h=mime-version:in-reply-to:references:date:message-id: subject:to:cc:reply-to:from; bh=Vqx8B94hNvjlnKKrXjWtf6h8Tg0/VRWnoZtzZvCzzoU=; b=vQ8laPYIJ/oh0J85VJqz6M9jCKe7Iyws4F97vXjYPiPRvQFWK21CjOZu zKdQDIxGB6ZxKJyPq5O8z/KAXANiqFFSEDsJ3SWJs9lVuTLIZULpYZdwf Ys8J9tbQHu+PE3soN7DytoCIlijRhT56hBzLvaM/YJPn0mQbnWkR0yNlS Q=; From: Pragash Vijayaragavan X-IronPort-AV: E=Sophos;i="5.45,395,1508817600"; d="scan'208,217";a="164382702" Received: from mail-ua0-f197.google.com ([209.85.217.197]) by smtp-server.rit.edu with ESMTP/TLS/AES128-GCM-SHA256; 12 Dec 2017 07:21:55 -0500 Received: by mail-ua0-f197.google.com with SMTP id n5so14314425uad.19 for ; Tue, 12 Dec 2017 04:21:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=sPIRobJp8dfEzosy32sPw2QQ1mJlb0dVlJIRFkH4CdQ=; b=c9EngxbzbxHd0eh5EFbQTonnOXGfJruItN9agE14vWyoTZFs+mXc6N8E7kzb+HF0T+ qUAROnU9I8Yxu/BVLwxW5VHGvbW/QGeTYRfhMJLjv0yCPZc+92aNVMd3fi37NAo3XS93 TN8sycSOg3FmuRnE+gX2WJNvbbsTOhXCPnPlULHO2ce4LqAQL3o/iI3/juT3GJWisVMk wy9Bs2Ggp8wleKJw9fRakHot1b9mzM408OVQ68szzAUdx3WQzcoNQIAAoB9gwt9Xwvzm 3o6MY5+p4J3dVZQKZkgeDvg3egw0JNZT9K8kDZwO6VcIgugk4rpX7rHO5+UICTa2fqvH l3Fw== X-Gm-Message-State: AKGB3mI08hhH9k0R5G0G9Me9oFIDBV1wlpEm73oV7MOXPm3/HA8d/p9L yh/7ob0QGlh7MHGoNPWEB/bSmkynqvRS5u+DuCopfs9IBN8prs7NlWwtd7WNLwX5f45gSGrLVuI UiLN3PIMfGM+gR2wBsPAydViys63iyw9t X-Received: by 10.159.53.133 with SMTP id t5mr4268057uad.26.1513081313853; Tue, 12 Dec 2017 04:21:53 -0800 (PST) X-Google-Smtp-Source: ACJfBovh04PgaoRUatLu3mGE54xGV3Zq4861xRTL3KVrK+SVqTNgBFjAVUF7D4TAiZ+nIkZDBB3+M6ZhM3Nd18kA1OE= X-Received: by 10.159.53.133 with SMTP id t5mr4268046uad.26.1513081313543; Tue, 12 Dec 2017 04:21:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.76.81 with HTTP; Tue, 12 Dec 2017 04:21:52 -0800 (PST) In-Reply-To: References: Date: Tue, 12 Dec 2017 07:21:52 -0500 Message-ID: To: "Hristo.Trifonov" Cc: "users@dpdk.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] port 0 not present on board error X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: pxv3620@rit.edu List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Dec 2017 12:21:55 -0000 Hi, im still getting the same error here is my dpdk_setup output Is it possible that my NICs dont support running dpdk. Network devices using DPDK-compatible driver ============================================ 0000:02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio unused=vfio-pci 0000:02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio unused=vfio-pci 0000:04:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio unused=vfio-pci 0000:04:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio unused=vfio-pci Network devices using kernel driver =================================== 0000:08:00.0 'I350 Gigabit Network Connection 1521' if=eth0 drv=igb unused=igb_uio,vfio-pci *Active* 0000:08:00.1 'I350 Gigabit Network Connection 1521' if=eth2 drv=igb unused=igb_uio,vfio-pci Other Network devices ===================== Crypto devices using DPDK-compatible driver =========================================== Crypto devices using kernel driver ================================== Other Crypto devices ==================== Eventdev devices using DPDK-compatible driver ============================================= Eventdev devices using kernel driver ==================================== Other Eventdev devices ====================== Mempool devices using DPDK-compatible driver ============================================ Mempool devices using kernel driver =================================== Other Mempool devices ===================== Press enter to continue ... Thanks, Pragash Vijayaragavan Grad Student at Rochester Institute of Technology email : pxv3620@rit.edu ph : 585 764 4662 On Tue, Dec 12, 2017 at 5:54 AM, Hristo.Trifonov wrote: > If your nb_ports = 0 shows that you haven't bind/provided any ports to > dpdk. > > Just verify that the ports that you want to use with dpdk (igb_uio) are > available on the machine. > This means that they are not used for anything else but dpdk. > > Before you attempt to bind any ports to igb_uio, from the terminal check > what ports are available on the machine using nmcli d or any other utility. > Load the igb_uio kernel module using the dpdk_setup script in > dpdk/usertools > Then use the dpdk_dev_bind or dpdk_setup script to bind the selected > ports to igb_uio. > Verify that the ports are using the igb_uio with the dpdk_setup script. > There is an option there for that. > > If you are using 2 ports (-p 0x3), use 2 lcores (-c 0xE) core 2 and core 3 > in this case. > Complete the cmd like this: > pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$> ./l3fwd -c > 0xE --no-huge -- -p 0x03 -L --config="(0,0,1),(1,0,2)" --parse-ptype > > If you want to use more lcores you must then change the -config option to > reflect the situation in terms of (port,queue,lcore) > > Hristo T. >