All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: n.nikolaev@virtualopensystems.com,
	virtualization@lists.linux-foundation.org
Subject: memory barriers in virtq.lua?
Date: Tue, 27 Jan 2015 18:01:26 +0200	[thread overview]
Message-ID: <20150127160126.GA10651@redhat.com> (raw)

Hi Nikolay,
I poked at src/lib/virtio/virtq.lua a bit -
I was surprised to find no explicit CPU memory
barriers in the virtq implementation.
These are typically required when using virtio
on smp machines - the spec actually mention where
barriers are necessary.
Are the barriers implicit somehow for lua?
I'd be curious to learn.


Thanks,

-- 
MST

             reply	other threads:[~2015-01-27 16:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 16:01 Michael S. Tsirkin [this message]
2015-01-28 10:27 ` memory barriers in virtq.lua? Nikolay Nikolaev
     [not found] ` <CADDJ2=M6hwFwooXqUjUc9+JxjW1sVYvKhY9dBavrmMUrej6Ysw@mail.gmail.com>
2015-04-07 14:22   ` [snabb-devel] " Luke Gorrie
     [not found]   ` <CADDJ2=M6hwFwooXqUjUc9+JxjW1sVYvKhY9dBavrmMUrej6Ysw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-07 14:22     ` Luke Gorrie
2015-04-07 15:30       ` Michael S. Tsirkin
     [not found]       ` <CAA2XHbcU0tV0NrBXT6oh6LOz7sKm9P8jqD1=T-ZgTahSVM_qwQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-07 15:30         ` Michael S. Tsirkin
     [not found]           ` <20150407172849-mutt-send-email-mst-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-04-08  3:40             ` Luke Gorrie
2015-04-08  3:40           ` Luke Gorrie
2015-04-08 15:15       ` [dpdk-dev] " Xie, Huawei
2015-04-08 15:15       ` [dpdk-dev] " Xie, Huawei
2015-04-09  3:12         ` Luke Gorrie
     [not found]           ` <CAA2XHbdNAB1ZsBFYHW7W1yhnkzaSixwKk4KvjU8G=7OLECpZhQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-09 15:00             ` [snabb-devel] " Xie, Huawei
2015-04-09 15:00           ` [dpdk-dev] " Xie, Huawei
2015-04-09  3:12         ` Luke Gorrie

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=20150127160126.GA10651@redhat.com \
    --to=mst@redhat.com \
    --cc=n.nikolaev@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 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.