From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Avi Kivity <avi@redhat.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC] virtio: put last seen used index into ring itself
Date: Thu, 20 May 2010 13:04:47 +0300 [thread overview]
Message-ID: <20100520100447.GC5717@redhat.com> (raw)
In-Reply-To: <201005201431.51142.rusty@rustcorp.com.au>
On Thu, May 20, 2010 at 02:31:50PM +0930, Rusty Russell wrote:
> Can we do better? The obvious idea is to try to get rid of last_used and
> used, and use the ring itself. We would use an invalid entry to mark the
> head of the ring.
>
> Any other thoughts?
> Rusty.
We also need a way to avoid interrupts at least while we are
processing the ring.
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org,
Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH RFC] virtio: put last seen used index into ring itself
Date: Thu, 20 May 2010 13:04:47 +0300 [thread overview]
Message-ID: <20100520100447.GC5717@redhat.com> (raw)
In-Reply-To: <201005201431.51142.rusty@rustcorp.com.au>
On Thu, May 20, 2010 at 02:31:50PM +0930, Rusty Russell wrote:
> Can we do better? The obvious idea is to try to get rid of last_used and
> used, and use the ring itself. We would use an invalid entry to mark the
> head of the ring.
>
> Any other thoughts?
> Rusty.
We also need a way to avoid interrupts at least while we are
processing the ring.
--
MST
next prev parent reply other threads:[~2010-05-20 10:08 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 20:58 [PATCH RFC] virtio: put last seen used index into ring itself Michael S. Tsirkin
2010-05-05 20:58 ` [Qemu-devel] " Michael S. Tsirkin
2010-05-05 21:18 ` Dor Laor
2010-05-05 21:18 ` Dor Laor
2010-05-05 21:18 ` [Qemu-devel] " Dor Laor
2010-05-06 2:31 ` Rusty Russell
2010-05-06 2:31 ` [Qemu-devel] " Rusty Russell
2010-05-06 6:19 ` Michael S. Tsirkin
2010-05-06 6:19 ` Michael S. Tsirkin
2010-05-06 6:19 ` [Qemu-devel] " Michael S. Tsirkin
2010-05-07 3:33 ` Rusty Russell
2010-05-07 3:33 ` [Qemu-devel] " Rusty Russell
2010-05-07 3:33 ` Rusty Russell
2010-05-09 21:06 ` Michael S. Tsirkin
2010-05-09 21:06 ` [Qemu-devel] " Michael S. Tsirkin
2010-05-09 21:06 ` Michael S. Tsirkin
2010-05-06 2:31 ` Rusty Russell
2010-05-06 10:00 ` [Qemu-devel] " Avi Kivity
2010-05-06 10:00 ` Avi Kivity
2010-05-06 10:00 ` Avi Kivity
2010-05-07 3:23 ` Rusty Russell
2010-05-07 3:23 ` Rusty Russell
2010-05-07 3:23 ` Rusty Russell
2010-05-07 3:23 ` Rusty Russell
2010-05-11 19:27 ` Avi Kivity
2010-05-11 19:27 ` Avi Kivity
2010-05-11 19:52 ` Michael S. Tsirkin
2010-05-11 19:52 ` Michael S. Tsirkin
2010-05-11 19:52 ` Michael S. Tsirkin
2010-05-19 7:39 ` Rusty Russell
2010-05-19 7:39 ` Rusty Russell
2010-05-19 7:39 ` Rusty Russell
2010-05-19 8:06 ` Avi Kivity
2010-05-19 8:06 ` Avi Kivity
2010-05-19 22:33 ` Michael S. Tsirkin
2010-05-19 22:33 ` Michael S. Tsirkin
2010-05-20 6:04 ` Avi Kivity
2010-05-20 6:04 ` Avi Kivity
2010-05-20 6:04 ` Avi Kivity
2010-05-19 22:33 ` Michael S. Tsirkin
2010-05-20 5:01 ` Rusty Russell
2010-05-20 5:01 ` Rusty Russell
2010-05-20 5:08 ` Rusty Russell
2010-05-20 5:08 ` Rusty Russell
2010-05-23 15:31 ` Michael S. Tsirkin
2010-05-23 15:31 ` Michael S. Tsirkin
2010-05-23 15:31 ` Michael S. Tsirkin
2010-05-23 15:41 ` Avi Kivity
2010-05-23 15:41 ` Avi Kivity
2010-05-23 15:51 ` Michael S. Tsirkin
2010-05-23 15:51 ` Michael S. Tsirkin
2010-05-23 16:03 ` Avi Kivity
2010-05-23 16:03 ` Avi Kivity
2010-05-23 16:30 ` Michael S. Tsirkin
2010-05-23 16:30 ` Michael S. Tsirkin
2010-05-24 6:37 ` Avi Kivity
2010-05-24 6:37 ` Avi Kivity
2010-05-24 6:37 ` Avi Kivity
2010-05-24 8:05 ` Michael S. Tsirkin
2010-05-24 8:05 ` Michael S. Tsirkin
2010-05-24 8:05 ` Michael S. Tsirkin
2010-05-24 11:00 ` Avi Kivity
2010-05-24 11:00 ` Avi Kivity
2010-05-24 11:00 ` Avi Kivity
2010-05-23 16:30 ` Michael S. Tsirkin
2010-05-23 17:28 ` Michael S. Tsirkin
2010-05-23 17:28 ` Michael S. Tsirkin
2010-05-23 17:28 ` Michael S. Tsirkin
2010-05-23 16:03 ` Avi Kivity
2010-05-23 15:51 ` Michael S. Tsirkin
2010-05-23 15:41 ` Avi Kivity
2010-05-23 15:56 ` Michael S. Tsirkin
2010-05-23 15:56 ` Michael S. Tsirkin
2010-05-23 15:56 ` Michael S. Tsirkin
2010-05-20 5:08 ` Rusty Russell
2010-05-20 7:00 ` Avi Kivity
2010-05-20 7:00 ` Avi Kivity
2010-05-20 14:34 ` Rusty Russell
2010-05-20 14:34 ` Rusty Russell
2010-05-20 14:34 ` Rusty Russell
2010-05-20 15:46 ` Avi Kivity
2010-05-20 15:46 ` Avi Kivity
2010-05-20 15:46 ` Avi Kivity
2010-05-20 7:00 ` Avi Kivity
2010-05-20 10:04 ` Michael S. Tsirkin [this message]
2010-05-20 10:04 ` Michael S. Tsirkin
2010-05-20 10:04 ` Michael S. Tsirkin
2010-05-20 5:01 ` Rusty Russell
2010-05-11 19:27 ` Avi Kivity
2010-05-11 18:46 ` Ryan Harper
2010-05-11 18:46 ` [Qemu-devel] " Ryan Harper
2010-05-11 19:48 ` Michael S. Tsirkin
2010-05-11 19:48 ` Michael S. Tsirkin
2010-05-11 19:48 ` [Qemu-devel] " Michael S. Tsirkin
2010-05-11 18:46 ` Ryan Harper
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=20100520100447.GC5717@redhat.com \
--to=mst@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.