All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
	qemu-devel@nongnu.org
Subject: Re: [PATCHv2-RFC 0/2] virtio: put last seen used index into ring itself
Date: Mon, 31 May 2010 09:36:00 +0200	[thread overview]
Message-ID: <4C0366E0.6040203@redhat.com> (raw)
In-Reply-To: <20100530112220.GA27611@redhat.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: [Qemu-devel] Re: [PATCHv2-RFC 0/2] virtio: put last seen used index into ring itself
Date: Mon, 31 May 2010 09:36:00 +0200	[thread overview]
Message-ID: <4C0366E0.6040203@redhat.com> (raw)
In-Reply-To: <20100530112220.GA27611@redhat.com>

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

  parent reply	other threads:[~2010-05-31  7:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 19:50 [PATCHv2-RFC 0/2] virtio: put last seen used index into ring itself Michael S. Tsirkin
2010-05-26 19:50 ` [Qemu-devel] " Michael S. Tsirkin
2010-05-26 19:50 ` [PATCHv2-RFC 1/2] virtio: support layout with avail ring before idx Michael S. Tsirkin
2010-05-26 19:50 ` Michael S. Tsirkin
2010-05-26 19:50   ` [Qemu-devel] " Michael S. Tsirkin
2010-05-26 19:50 ` [PATCHv2-RFC 2/2] virtio: publish used idx Michael S. Tsirkin
2010-05-26 19:50   ` [Qemu-devel] " Michael S. Tsirkin
2010-05-26 19:50 ` Michael S. Tsirkin
2010-05-27 12:07 ` [PATCHv2-RFC 0/2] virtio: put last seen used index into ring itself Avi Kivity
2010-05-27 12:07 ` Avi Kivity
2010-05-27 12:07   ` [Qemu-devel] " Avi Kivity
2010-05-27 13:59   ` Michael S. Tsirkin
2010-05-27 13:59   ` Michael S. Tsirkin
2010-05-27 13:59     ` [Qemu-devel] " Michael S. Tsirkin
2010-05-28  9:56 ` Jes Sorensen
2010-05-28  9:56 ` Jes Sorensen
2010-05-28  9:56   ` [Qemu-devel] " Jes Sorensen
2010-05-30 11:22   ` Michael S. Tsirkin
2010-05-30 11:22     ` [Qemu-devel] " Michael S. Tsirkin
2010-05-31  7:36     ` Jes Sorensen
2010-05-31  7:36     ` Jes Sorensen [this message]
2010-05-31  7:36       ` [Qemu-devel] " Jes Sorensen
2010-05-31 13:29       ` Michael S. Tsirkin
2010-05-31 13:29         ` [Qemu-devel] " Michael S. Tsirkin
2010-05-31 13:29       ` Michael S. Tsirkin
2010-05-30 11:22   ` Michael S. Tsirkin
2010-05-31  7:46 ` Rusty Russell
2010-05-31  7:46 ` Rusty Russell
2010-05-31  7:46   ` [Qemu-devel] " Rusty Russell
2010-05-31 12:20   ` Michael S. Tsirkin
2010-05-31 12:20   ` Michael S. Tsirkin
2010-05-31 12:20     ` [Qemu-devel] " Michael S. Tsirkin
2010-06-02 20:39   ` Jes Sorensen
2010-06-02 20:39   ` Jes Sorensen
2010-06-02 20:39     ` Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2010-05-26 19:50 Michael S. Tsirkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C0366E0.6040203@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.