From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.digiweb.ie (smtp2.digiweb.ie [83.147.160.14]) by dpdk.org (Postfix) with ESMTP id 393C47F4D for ; Fri, 7 Nov 2014 13:27:28 +0100 (CET) Received: from statler.emutex.com (unknown [92.51.199.138]) by smtp.digiweb.ie (Postfix) with ESMTP id CE36D29006B for ; Fri, 7 Nov 2014 12:36:59 +0000 (GMT) Received: from [10.10.64.102] by statler.emutex.com with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1Xmimh-0000Yd-Mg for dev@dpdk.org; Fri, 07 Nov 2014 12:36:59 +0000 Message-ID: <545CBCE0.2030806@emutex.com> Date: Fri, 07 Nov 2014 12:36:48 +0000 From: Nicolas Pernas Maradei User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: dev@dpdk.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [dpdk-dev] White listing a virtual device X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 12:27:28 -0000 Hi, I'm currently using the --vdev option to create virtual devices, mainly for testing. I noticed that these virtual devices are not being white-listed any more. That was the original behaviour when the option was called --use-device. Instead of that the virtual device is being added to the device list along with the real ones. You can see this behaviour by running testpmd as shown below. I have 4 Niantics on my system and they are all bound to igb_uio driver. You can see the 5 ports being reported. Now, the --pci-whitelist argument lets you white list a device but it only accepts a PCI address as an option. My question is, how do you white list a virtual device? Did this feature get dropped when the --use-device was split into --vdev and --pci-whitelist back in March/April or is this just an unhandled corner case? [nico dpdk]((v1.7.1))# sudo ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 3 --vdev=eth_pcap0,rx_pcap=eth_ipv4.pcap,tx_pcap=/dev/null ... Configuring Port 0 (socket 0) Port 0: 00:00:00:01:02:03 <---- PCAP virtual device Configuring Port 1 (socket 0) Port 1: 90:E2:BA:6D:EC:D4 Configuring Port 2 (socket 0) Port 2: 90:E2:BA:6D:EC:D5 Configuring Port 3 (socket 0) Port 3: 90:E2:BA:74:6C:B4 Configuring Port 4 (socket 0) Port 4: 90:E2:BA:74:6C:B5 Checking link statuses... Port 0 Link Up - speed 10000 Mbps - full-duplex Port 1 Link Up - speed 10000 Mbps - full-duplex Port 2 Link Up - speed 10000 Mbps - full-duplex Port 3 Link Up - speed 10000 Mbps - full-duplex Port 4 Link Up - speed 10000 Mbps - full-duplex Done No commandline core given, start packet forwarding ... Thanks, Nico.