From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 18959B62 for ; Wed, 23 Dec 2015 03:39:05 +0100 (CET) Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id 23FE2694; Wed, 23 Dec 2015 02:39:04 +0000 (UTC) Received: from pxdev.xzpeter.org (vpn1-6-193.pek2.redhat.com [10.72.6.193]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tBN2cruP000501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 22 Dec 2015 21:38:58 -0500 Date: Wed, 23 Dec 2015 10:38:52 +0800 From: Peter Xu To: Yuanhan Liu Message-ID: <20151223023852.GD1694@pxdev.xzpeter.org> References: <20151222035041.GA7532@pxdev.xzpeter.org> <20151222070029.GO18863@yliu-dev.sh.intel.com> <20151222082338.GG7532@pxdev.xzpeter.org> <20151222083246.GT18863@yliu-dev.sh.intel.com> <20151222095641.GH7532@pxdev.xzpeter.org> <20151222113912.GA30780@pxdev.xzpeter.org> <20151223015554.GC1694@pxdev.xzpeter.org> <20151223020949.GV18863@yliu-dev.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20151223020949.GV18863@yliu-dev.sh.intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22 Cc: DPDK Dev Subject: Re: [dpdk-dev] [Question] How pmd virtio works without UIO? 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: Wed, 23 Dec 2015 02:39:05 -0000 On Wed, Dec 23, 2015 at 10:09:49AM +0800, Yuanhan Liu wrote: > Why can't we simply quit at pci_scan_one, once finding that it's not > bond to uio (or similar stuff)? That would be generic enough, that we > don't have to do similar checks for each new pmd driver. > > Or, am I missing something? It seems that ioport way to play with virtio devices do not require any PCI wrapper layer like UIO/VFIO? Please check virtio_resource_init(). > > > > I guess there might be two problems? Which are: > > > > 1. How user avoid DPDK taking over virtio devices that they do not > > want for IO (chooses which device to use) > > Isn't that what's the 'binding/unbinding' for? > > > 2. Driver conflict between virtio PMD in DPDK, and virtio-pci in > > kernel (happens on every virtio device that DPDK uses) > > If you unbinded the kernel driver first, which is the suggested (or > must?) way to use DPDK, that will not happen. Yes, maybe we should unbind it first. I am just not sure what will happen if not. Peter