From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: virtio-net: bind systematically on all non blacklisted virtio-net devices Date: Thu, 01 Oct 2015 17:08:05 +0200 Message-ID: <1569737.1ykgx8Ghpo@xps13> References: <55EE9AFE.1070202@qosmos.com> <55F177D4.5010701@qosmos.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Franck Baudin , "Ouyang, Changchun" , huawei.xie@intel.com Return-path: Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by dpdk.org (Postfix) with ESMTP id 3B4446A87 for ; Thu, 1 Oct 2015 17:09:13 +0200 (CEST) Received: by wicge5 with SMTP id ge5so34525059wic.0 for ; Thu, 01 Oct 2015 08:09:13 -0700 (PDT) In-Reply-To: <55F177D4.5010701@qosmos.com> 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" 2015-09-10 14:30, Franck Baudin: > On 09/09/15 04:11, Ouyang, Changchun wrote: > >> 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. > > > > It allows virtio-pmd not necessarily depend on igb_uio, this is which characteristic other pmd drivers don't have. > > Thanks for your answer, > > So this is the expected behaviour: all virtio interfaces are bound to > the pmd driver. > > Don't you think that dpdk_nic_bind.py should reflect the driver > behaviour, and that the virtio documentation (still referencing igb_uio) > be amended? Yes maybe that the documentation must be updated. Anyone?