From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org (bombadil.infradead.org. [2607:7c80:54:e::133]) by gmr-mx.google.com with ESMTPS id q68si57370ywg.0.2019.01.17.07.15.44 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 17 Jan 2019 07:15:44 -0800 (PST) Date: Thu, 17 Jan 2019 07:15:29 -0800 From: Christoph Hellwig Subject: Re: [PATCH 0/8] Virtio-over-PCIe on non-MIC Message-ID: <20190117151529.GA3471@infradead.org> References: <20190116163253.23780-1-vincent.whitchurch@axis.com> <20190117105441.eqediwlekofp2srg@axis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: To: Arnd Bergmann Cc: Vincent Whitchurch , sudeep.dutt@intel.com, ashutosh.dixit@intel.com, gregkh , Linux Kernel Mailing List , Kishon Vijay Abraham I , Lorenzo Pieralisi , linux-pci , linux-ntb@googlegroups.com, Jon Mason , Dave Jiang , Allen Hubbe List-ID: On Thu, Jan 17, 2019 at 01:39:27PM +0100, Arnd Bergmann wrote: > Can you describe how you expect a VOP device over NTB or > PCIe-endpoint would get created, configured and used? > Is there always one master side that is responsible for creating > virtio devices on it, with the slave side automatically attaching to > them, or can either side create virtio devices? Is there any limit on > the number of virtio devices or queues within a VOP device? For VOP device over NTB your configure your device using configfs on one side, and for the other side it will just show up like any other PCIe device, because it is.