From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [RFC 7/11] virtio_pci: new, capability-aware driver. Date: Thu, 12 Jan 2012 07:29:54 +0200 Message-ID: <20120112052953.GB10319@redhat.com> References: <20111219091324.GA19535@redhat.com> <871us0om2t.fsf@rustcorp.com.au> <20111220113718.GF3913@redhat.com> <878vm6daqy.fsf@rustcorp.com.au> <20120110170334.GA18404@redhat.com> <8762gj6q5r.fsf@rustcorp.com.au> <20120111102129.GC20988@redhat.com> <1326316422.23910.154.camel@pasglop> <20120111221349.GD27292@redhat.com> <1326322599.23910.167.camel@pasglop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1326322599.23910.167.camel@pasglop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Benjamin Herrenschmidt Cc: Christian Borntraeger , Sasha Levin , Pawel Moll , virtualization List-Id: virtualization@lists.linuxfoundation.org On Thu, Jan 12, 2012 at 09:56:39AM +1100, Benjamin Herrenschmidt wrote: > I'd suggest doing a simple user space app that creates such a ring, > forks, and produce / consume. We can then run that through perf and > analyze the cache behaviour, maximum throughput, etc.... > > Cheers, > Ben. Sure. You can also use my tools/virtio hack: this rebuilds virtio ring code in userspace, has the advantage of reusing actual kernel code, so it's up to date, has same barriers, etc. -- MST