From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f47.google.com (mail-oi0-f47.google.com [209.85.218.47]) by dpdk.org (Postfix) with ESMTP id AA91C23D for ; Wed, 8 Aug 2018 13:14:51 +0200 (CEST) Received: by mail-oi0-f47.google.com with SMTP id 13-v6so3075731ois.1 for ; Wed, 08 Aug 2018 04:14:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6JDbnIExh55cAWlIfDAqkukTLYIH8iSqWt+6xOwtjy8=; b=O2SUnZFRDBHOS7jhPDrRkFNWV8S4uKjqcf10u/LhRbtweeamemt/PWZsyyXOsmNI5n GLArgWFhO/2CTc4CAmT/E8lDd+x2746bmU7V1ilmM/FkfiH2eBUB8CBX7Er6/RL58A7Z ACCVwJxeLBtfAg7tARbhBMNVGEMfZ6IBAC6oqdCF4ap/Sc0WXeshmp7Rh6k3NDuFJkdd zbN71Oef3AuFh6ZvPi9FKOs64GneWXoyMMTmgOWzMieRL7BqF9aTaQjqtZQZo8HR+7ci gvaAN6D9idDaL1niVc1+1Ir0cmXxoEOiaqVEckC6VYwGZQQ3m0+BvQv/dXZaIdFvejMB 08sw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6JDbnIExh55cAWlIfDAqkukTLYIH8iSqWt+6xOwtjy8=; b=miXN/njMOKt9P0957zfZCwzlfJbnxd9RfDHgnaIr+KUApmLpiMCSHAEXNwiQtoKLAE BZy1853my56aLP/GSRTKokQY1zoZKKDx1k36Lf6IuZWpWyoy7XxZd1KIno93U2e9cGnH YOR9522zAgtKY/lloTajoA/YznRztde2fpmk5g5AJf9vDm0+mg8fw5rLg4Bh25YXMRX/ rDAAUiUPDy0JXtoka4nxyPjJ2oJnwm+iQ9mClPt+2GDGb33Pai2+sVCUKzINU4rXX0mY PbukmDQEJRzQqzSCCF+P7EozGjPut/SwHaxARF4gqpkzKpDihIot8kQK1jm9+fvMO1Ow ewhQ== X-Gm-Message-State: AOUpUlFjCunVRVP46pbfy/Ttu2D4Gm4Gi5/c/dg1L5vSK2HHFvG52OGR DhW3QCUvKeHqv6Q6BhlPhg0ZwV2yV5wynLSaWWQ= X-Google-Smtp-Source: AA+uWPz5kpLmMsMX64na+OV7b/iNnUYfhy1FQEm7te9u8ctrMeAJ8LBqt8X9sqN40pQBjRD4nqwGTgnrJ4P8b8MxPX8= X-Received: by 2002:aca:3882:: with SMTP id f124-v6mr2298585oia.195.1533726889546; Wed, 08 Aug 2018 04:14:49 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:5a02:0:0:0:0:0 with HTTP; Wed, 8 Aug 2018 04:14:28 -0700 (PDT) In-Reply-To: <252c1462-2086-bff3-febb-1f7c7b80b2f1@tssg.org> References: <252c1462-2086-bff3-febb-1f7c7b80b2f1@tssg.org> From: yogev ch Date: Wed, 8 Aug 2018 14:14:28 +0300 Message-ID: To: Sidhant Hasija Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Error attaching dpdk ports to ovs 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: Wed, 08 Aug 2018 11:14:51 -0000 What's your use case? As you're using your own laptop, I assume you're not testing performance and large traffic volumes right now. If you're about functionality games you can use the '--vdev' option, instead of compiling OVS with DPDK. '--vdev' let you use through libpcap your machine's interfaces (from ifconfig. i.e. eth0) or pcap files. On Wed, Aug 8, 2018 at 1:30 PM, Sidhant Hasija wrote: > Hello dpdk-users, > > I am very much new to dpdk usage and development, and is eager to dive > deep into it. > > My laptop has a Realtek NIC (RTL8101/2/6E), which going by the list of > supported hardware pages is unsupported as also confirmed by the following > error while starting ethtool application. Prior to starting the > application, my ethernet card was successfully bound to vfio-pci module, > and I also tested with binding to igb-uio module. > > EAL: Detected 4 lcore(s) > EAL: No free hugepages reported in hugepages-1048576kB > EAL: Probing VFIO support... > EAL: VFIO support initialized > Number of NICs: 0 > EAL: Error - exiting with code: 1 > Cause: No available NIC ports! > > Unable to move ahead due to NIC not being supported, I tried to setup ovs > with dpdk. However, while attaching a port to ovs netdev bridge as written > in the getting started guide, I get the following error. > > $ ovs-vsctl add-br br0 -- set bridge br0 datapath_type=netdev > $ ovs-vsctl add-port br0 brp1 -- set Interface brp1 type=dpdk > options:dpdk-devargs=0000:06:00.0 > > 2018-08-08T10:09:33.136Z|00062|dpdk|ERR|EAL: Driver cannot attach the > device (0000:06:00.0) > 2018-08-08T10:09:33.136Z|00063|dpdk|ERR|EAL: No port found for device > (0000:06:00.0) > 2018-08-08T10:09:33.136Z|00064|netdev_dpdk|WARN|Error attaching device > '0000:06:00.0' to DPDK > 2018-08-08T10:09:33.136Z|00065|netdev|WARN|brp1: could not set > configuration (Invalid argument) > > I tried with 2.9.2 and dpdk 17.11.0, as well with dpdk 18 and ovs master > (2.10). > > I think the problem here is that I am trying to attach a physical > interface to ovs bridge using its PCI address which is either not present > or unsupported. > > It will be really helpful if you can please provide inputs on how to use > dpdk without a physical interface and the direction to troubleshoot above > ovs error. I dont have any specific use-case as yet, but just want to dive > deep into dpdk and start learning. > > Many Thanks, > Sidhant Hasija > > >