From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [Qemu-devel] Re: [PATCH 2/3] virtio network device
Date: Sat, 08 Dec 2007 15:59:19 -0600 [thread overview]
Message-ID: <475B13B7.9040807@codemonkey.ws> (raw)
In-Reply-To: <200712081322.39762.paul@codesourcery.com>
Paul Brook wrote:
>> virtio makes things a bit trickier though. There's a shared ring queue
>> between the host and guest. The ring queue is lock-less and depends on
>> the ability to atomically increment ring queue indices to be SMP safe.
>> Using a copy-API wouldn't be a problem for QEMU since the host and guest
>> are always running in lock-step. A copy API is actually needed to deal
>> with differing host/guest alignment and endianness.
>>
>
> That seems a rather poor design choice, as many architectures don't have an
> atomic increment instruction. Oh well.
>
Sorry, I should have been more clear. An atomic increment isn't needed,
just an atomic store.
Regards,
Anthony Liguori
> Paul
>
>
>
>
prev parent reply other threads:[~2007-12-08 21:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 21:54 [Qemu-devel] [PATCH 2/3] virtio network device Anthony Liguori
2007-12-04 22:12 ` Anthony Liguori
2007-12-04 23:49 ` [Qemu-devel] " Dor Laor
2007-12-05 17:18 ` Anthony Liguori
2007-12-05 17:44 ` Paul Brook
2007-12-05 20:20 ` Anthony Liguori
2007-12-06 9:27 ` Jamie Lokier
2007-12-08 13:22 ` Paul Brook
2007-12-08 14:09 ` Jamie Lokier
2007-12-08 16:45 ` Paul Brook
2007-12-08 19:52 ` Blue Swirl
2007-12-08 21:55 ` Jamie Lokier
2007-12-08 22:02 ` Anthony Liguori
2007-12-12 1:24 ` Rusty Russell
2007-12-12 1:40 ` Anthony Liguori
2007-12-18 2:31 ` Rusty Russell
2007-12-08 21:59 ` Anthony Liguori [this message]
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=475B13B7.9040807@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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.