All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ilya Maximets <i.maximets@samsung.com>
Cc: Shahaf Shuler <shahafs@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Xiao Wang <xiao.w.wang@intel.com>,
	"jfreimann@redhat.com" <jfreimann@redhat.com>,
	Tiwei Bie <tiwei.bie@intel.com>,
	Zhihong Wang <zhihong.wang@intel.com>,
	Jason Wang <jasowang@redhat.com>,
	"xiaolong.ye@intel.com" <xiaolong.ye@intel.com>,
	"alejandro.lucero@netronome.com" <alejandro.lucero@netronome.com>,
	Daniel Marcovitch <danielm@mellanox.com>
Subject: Re: [PATCH v2] net/virtio: add platform memory ordering feature support
Date: Wed, 9 Jan 2019 10:50:07 -0500	[thread overview]
Message-ID: <20190109104855-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <2832c88f-9b43-997c-5937-ef5ae6482fd5@samsung.com>

On Wed, Jan 09, 2019 at 05:34:38PM +0300, Ilya Maximets wrote:
> virtio_mb() is really heavy. I'd like to avoid it somehow, but I don't
> know how to do this yet.

Linux driver doesn't avoid it either.

-- 
MST

  reply	other threads:[~2019-01-09 15:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20181214153817eucas1p19a41cdd791879252e1f3a5d77c427845@eucas1p1.samsung.com>
2018-12-14 15:38 ` [PATCH] net/virtio: add platform memory ordering feature support Ilya Maximets
2018-12-14 17:00   ` Michael S. Tsirkin
2018-12-14 17:23     ` Ilya Maximets
2018-12-26 16:37   ` [PATCH v2] " Ilya Maximets
2018-12-27 10:07     ` Shahaf Shuler
2019-01-09 14:34       ` Ilya Maximets
2019-01-09 15:50         ` Michael S. Tsirkin [this message]
2019-01-10 20:36           ` Shahaf Shuler
2019-01-15  6:33             ` Shahaf Shuler
2019-01-15  8:29               ` Ilya Maximets
2019-01-15  8:55                 ` Shahaf Shuler
2019-01-15 10:23                   ` Ilya Maximets
2019-02-12 17:50                   ` Michael S. Tsirkin
2019-01-09 14:50     ` [PATCH v3 0/3] Missing barriers and VIRTIO_F_ORDER_PLATFORM Ilya Maximets
2019-01-09 14:50       ` [PATCH v3 1/3] net/virtio: add missing barrier before reading the flags Ilya Maximets
2019-01-10 14:31         ` Maxime Coquelin
2019-01-09 14:50       ` [PATCH v3 2/3] net/virtio: update memory ordering comment for vq notify Ilya Maximets
2019-01-10  8:19         ` Gavin Hu (Arm Technology China)
2019-01-10  9:18           ` Maxime Coquelin
2019-01-10  9:55             ` Ilya Maximets
2019-01-10 14:56               ` Michael S. Tsirkin
2019-01-10 14:31         ` Maxime Coquelin
2019-01-09 14:50       ` [PATCH v3 3/3] net/virtio: add platform memory ordering feature support Ilya Maximets
2019-01-10 14:31         ` Maxime Coquelin
2019-01-09 14:55       ` [PATCH v3 0/3] Missing barriers and VIRTIO_F_ORDER_PLATFORM Michael S. Tsirkin
2019-01-09 15:24         ` Ilya Maximets
2019-01-09 16:53           ` Ferruh Yigit
2019-01-10 15:19         ` Maxime Coquelin

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=20190109104855-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=danielm@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=i.maximets@samsung.com \
    --cc=jasowang@redhat.com \
    --cc=jfreimann@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=shahafs@mellanox.com \
    --cc=tiwei.bie@intel.com \
    --cc=xiao.w.wang@intel.com \
    --cc=xiaolong.ye@intel.com \
    --cc=zhihong.wang@intel.com \
    /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.