From: "Xie, Huawei" <huawei.xie@intel.com>
To: Luke Gorrie <luke@snabb.co>,
"snabb-devel@googlegroups.com" <snabb-devel@googlegroups.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [dpdk-dev] [snabb-devel] Re: memory barriers in virtq.lua?
Date: Thu, 9 Apr 2015 15:00:32 +0000 [thread overview]
Message-ID: <C37D651A908B024F974696C65296B57B0F4300E6@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <CAA2XHbdNAB1ZsBFYHW7W1yhnkzaSixwKk4KvjU8G=7OLECpZhQ@mail.gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Luke Gorrie
> Sent: Thursday, April 09, 2015 11:13 AM
> To: snabb-devel@googlegroups.com
> Cc: dev@dpdk.org; VirtualOpenSystems Technical Team; Michael S. Tsirkin;
> virtualization@lists.linux-foundation.org
> Subject: Re: [dpdk-dev] [snabb-devel] Re: memory barriers in virtq.lua?
>
> Howdy,
>
> On 8 April 2015 at 17:15, Xie, Huawei <huawei.xie@intel.com> wrote:
>
> > luke:
> > 1. host read the flag. 2 guest toggles the flag 3.guest checks the used.
> > 4. host update used.
> > Is this your case?
> >
>
> Yep, that is exactly the case I mean.
Thanks. Will provide fix after evaluation.
>
> Cheers,
> -Luke
prev parent reply other threads:[~2015-04-09 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150127160126.GA10651@redhat.com>
[not found] ` <CADDJ2=M6hwFwooXqUjUc9+JxjW1sVYvKhY9dBavrmMUrej6Ysw@mail.gmail.com>
2015-04-07 14:22 ` Luke Gorrie
2015-04-07 15:30 ` Michael S. Tsirkin
2015-04-08 3:40 ` Luke Gorrie
2015-04-08 15:15 ` Xie, Huawei
2015-04-09 3:12 ` Luke Gorrie
2015-04-09 15:00 ` Xie, Huawei [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=C37D651A908B024F974696C65296B57B0F4300E6@SHSMSX101.ccr.corp.intel.com \
--to=huawei.xie@intel.com \
--cc=dev@dpdk.org \
--cc=luke@snabb.co \
--cc=mst@redhat.com \
--cc=snabb-devel@googlegroups.com \
--cc=tech@virtualopensystems.com \
--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).