From: Tiwei Bie <tiwei.bie@intel.com>
To: Ilya Maximets <i.maximets@samsung.com>
Cc: dev@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Zhihong Wang <zhihong.wang@intel.com>,
Jens Freimann <jfreimann@redhat.com>
Subject: Re: [PATCH 0/3] net/virtio: missing/wrong read barriers.
Date: Fri, 25 Jan 2019 12:43:46 +0800 [thread overview]
Message-ID: <20190125044345.GA30156@dpdk-tbie> (raw)
In-Reply-To: <20190124165902.24178-1-i.maximets@samsung.com>
On Thu, Jan 24, 2019 at 07:58:59PM +0300, Ilya Maximets wrote:
> Ilya Maximets (3):
> net/virtio: fix improper read barriers on packed Tx cleanup
> net/virtio: add barriers for extra descriptors on Rx split
> net/virtio: add missing read barrier for packed dequeue
>
> drivers/net/virtio/virtio_rxtx.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Reviewed-by: Tiwei Bie <tiwei.bie@intel.com>
next prev parent reply other threads:[~2019-01-25 4:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190124165910eucas1p212dd655a34f42e11048e85eb17c7d0d0@eucas1p2.samsung.com>
2019-01-24 16:58 ` [PATCH 0/3] net/virtio: missing/wrong read barriers Ilya Maximets
2019-01-24 16:59 ` [PATCH 1/3] net/virtio: fix improper read barriers on packed Tx cleanup Ilya Maximets
2019-01-25 12:43 ` Jens Freimann
2019-01-25 12:49 ` Jens Freimann
2019-01-24 16:59 ` [PATCH 2/3] net/virtio: add barriers for extra descriptors on Rx split Ilya Maximets
2019-01-24 16:59 ` [PATCH 3/3] net/virtio: add missing read barrier for packed dequeue Ilya Maximets
2019-01-25 12:44 ` Jens Freimann
2019-01-25 12:48 ` Jens Freimann
2019-01-25 4:43 ` Tiwei Bie [this message]
2019-01-25 15:50 ` [PATCH 0/3] net/virtio: missing/wrong read barriers Maxime Coquelin
2019-02-08 18:04 ` 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=20190125044345.GA30156@dpdk-tbie \
--to=tiwei.bie@intel.com \
--cc=dev@dpdk.org \
--cc=i.maximets@samsung.com \
--cc=jfreimann@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.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.