From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jes Sorensen Subject: Re: [PATCHv2-RFC 0/2] virtio: put last seen used index into ring itself Date: Mon, 31 May 2010 09:36:00 +0200 Message-ID: <4C0366E0.6040203@redhat.com> References: <4BFF9366.5090103@redhat.com> <20100530112220.GA27611@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Rusty Russell , linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, kvm@vger.kernel.org, qemu-devel@nongnu.org To: "Michael S. Tsirkin" Return-path: In-Reply-To: <20100530112220.GA27611@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 05/30/10 13:22, Michael S. Tsirkin wrote: > On Fri, May 28, 2010 at 11:56:54AM +0200, Jes Sorensen wrote: >> It looks pretty good to me, however one thing I have been thinking of >> while reading through it: >> >> Rather than storing a pointer within the ring struct, pointing into a >> position within the same struct. How about storing a byte offset instead >> and using a cast to get to the pointer position? That would avoid the >> pointer dereference, which is less effective cache wise and harder for >> the CPU to predict. >> >> Not sure whether it really matters performance wise, just a thought. > > I think this won't work: when PUBLUSH_USED_IDX is negotiated, > the pointer is to within the ring. Hmmm shame, it would be a nice optimization. Maybe it's time to introduce the v2 ring format, rather than having adding more kludges to the existing one? Cheers, Jes