From mboxrd@z Thu Jan 1 00:00:00 1970 From: Franck Baudin Subject: virtio-net: bind systematically on all non blacklisted virtio-net devices Date: Tue, 8 Sep 2015 10:23:26 +0200 Message-ID: <55EE9AFE.1070202@qosmos.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit To: "dev@dpdk.org" Return-path: Received: from mc24.lon.server.colt.net (mc24.lon.server.colt.net [212.74.77.104]) by dpdk.org (Postfix) with ESMTP id 04D218DA8 for ; Tue, 8 Sep 2015 10:23:28 +0200 (CEST) Received: from mc24.lon.server.colt.net (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 84EBDDE103 for ; Tue, 8 Sep 2015 09:23:27 +0100 (BST) Received: from mx3.qosmos.com (unknown [195.68.92.43]) by mc24.lon.server.colt.net (Postfix) with ESMTPS id 67FEBDE0FD for ; Tue, 8 Sep 2015 09:23:27 +0100 (BST) List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi, virtio-net driver bind on all virtio-net devices, even if the devices are used by the kernel (leading to kernel soft-lookup/panic). One way around is to blacklist the ports in use by Linux. This is the case since v2.0.0, in fact since commit da978dfdc43b59e290a46d7ece5fd19ce79a1162 and the removal of the RTE_PCI_DRV_NEED_MAPPING driver flag. Questions: 1/ Is it the expected behaviour? 2/ Why is it different from vmxnet3 pmd? In other words, should't we re-add the RTE_PCI_DRV_NEED_MAPPING to virtio pmd or remove it from pmxnet3 pmd? 3/ If this is the expected behaviour, shouldn't we update dpdk_nic_bind.py (binding status irrelevant for virtio) tool and the documentation (mentioning igb_uio while misleading and useless)? Thanks! Best Regards, Franck