qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: qemu-devel@nongnu.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: [Qemu-devel] Re: [PATCH RFC] virtio: put last seen used index into ring itself
Date: Mon, 10 May 2010 00:06:52 +0300	[thread overview]
Message-ID: <20100509210652.GB21338@redhat.com> (raw)
In-Reply-To: <201005071303.29129.rusty@rustcorp.com.au>

On Fri, May 07, 2010 at 01:03:28PM +0930, Rusty Russell wrote:
> On Thu, 6 May 2010 03:49:46 pm Michael S. Tsirkin wrote:
> > Now, I also added an mb() in guest between read and write so
> > that last used index write can not get ahead of used index read.
> > It does feel good to have it there, but I can not say why
> > it's helpful. Works fine without it, but then these
> > subtle races might be hard to trigger. What do you think?
> 
> I couldn't see that in the patch?  I don't think it's necessary
> though, since the write of depends last_used depends on the read of
> used (and no platform we care about would reorder such a thing).

Well, there's no data dependency, is there?

> I'm reasonably happy, but we should write some convenient test for
> missing interrupts.
> 
> I'm thinking of a sender which does a loop: blasts 1MB of UDP packets,
> then prints the time and sleep(1).  The receiver would print the time
> every 1MB of received data.  The two times should almost exactly correspond.
> 
> Assuming that the network doesn't overflow and lose stuff, this should
> identify any missing wakeup/interrupts (depending on direction used).
> 
> Cheers,
> Rusty.

  reply	other threads:[~2010-05-09 21:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 20:58 [Qemu-devel] [PATCH RFC] virtio: put last seen used index into ring itself Michael S. Tsirkin
2010-05-05 21:18 ` [Qemu-devel] " Dor Laor
2010-05-06  2:31 ` Rusty Russell
2010-05-06  6:19   ` Michael S. Tsirkin
2010-05-07  3:33     ` Rusty Russell
2010-05-09 21:06       ` Michael S. Tsirkin [this message]
2010-05-06 10:00 ` [Qemu-devel] " Avi Kivity
2010-05-07  3:23   ` Rusty Russell
2010-05-11 19:27     ` Avi Kivity
2010-05-11 19:52       ` Michael S. Tsirkin
2010-05-19  7:39       ` Rusty Russell
2010-05-19  8:06         ` Avi Kivity
2010-05-19 22:33           ` Michael S. Tsirkin
2010-05-20  6:04             ` Avi Kivity
2010-05-20  5:01           ` Rusty Russell
2010-05-20  5:08             ` Rusty Russell
2010-05-23 15:31               ` Michael S. Tsirkin
2010-05-23 15:41                 ` Avi Kivity
2010-05-23 15:51                   ` Michael S. Tsirkin
2010-05-23 16:03                     ` Avi Kivity
2010-05-23 16:30                       ` Michael S. Tsirkin
2010-05-24  6:37                         ` Avi Kivity
2010-05-24  8:05                           ` Michael S. Tsirkin
2010-05-24 11:00                             ` Avi Kivity
2010-05-23 17:28                       ` Michael S. Tsirkin
2010-05-23 15:56               ` Michael S. Tsirkin
2010-05-20  7:00             ` Avi Kivity
2010-05-20 14:34               ` Rusty Russell
2010-05-20 15:46                 ` Avi Kivity
2010-05-20 10:04             ` Michael S. Tsirkin
2010-05-11 18:46 ` [Qemu-devel] " Ryan Harper
2010-05-11 19:48   ` 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=20100509210652.GB21338@redhat.com \
    --to=mst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).