From: "Yang, Zhiyong" <zhiyong.yang@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
"Tan, Jianfeng" <jianfeng.tan@intel.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"Bie, Tiwei" <tiwei.bie@intel.com>,
"jfreimann@redhat.com" <jfreimann@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC v2 1/3] vhost: invalidate vring addresses in cleanup_vq()
Date: Wed, 28 Feb 2018 06:35:06 +0000 [thread overview]
Message-ID: <E182254E98A5DA4EB1E657AC7CB9BD2A8B055ABB@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <20180227143441.6471-2-maxime.coquelin@redhat.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Maxime Coquelin
> Sent: Tuesday, February 27, 2018 10:35 PM
> To: Tan, Jianfeng <jianfeng.tan@intel.com>; stefanha@redhat.com; Bie,
> Tiwei <tiwei.bie@intel.com>; jfreimann@redhat.com; dev@dpdk.org
> Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
> Subject: [dpdk-dev] [RFC v2 1/3] vhost: invalidate vring addresses in
> cleanup_vq()
>
> When cleaning-up the virtqueue, we also need to invalidate its addresses to
> be sure outdated addresses won't be used later.
>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> Reviewed-by: Jens Freimann <jfreimann@redhat.com>
> ---
Reviewed-by: Zhiyong Yang <zhiyong.yang@intel.com>
next prev parent reply other threads:[~2018-02-28 6:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 14:34 [dpdk-dev] [RFC v2 0/3] host: multiqueue improvements Maxime Coquelin
2018-02-27 14:34 ` [dpdk-dev] [RFC v2 1/3] vhost: invalidate vring addresses in cleanup_vq() Maxime Coquelin
2018-02-28 6:35 ` Yang, Zhiyong [this message]
2018-02-27 14:34 ` [dpdk-dev] [RFC v2 2/3] vhost: add SET_VIRTIO_STATUS support Maxime Coquelin
2018-02-27 14:34 ` [dpdk-dev] [RFC v2 3/3] vhost_user: work around invalid rings addresses sent by QEMU 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=E182254E98A5DA4EB1E657AC7CB9BD2A8B055ABB@BGSMSX101.gar.corp.intel.com \
--to=zhiyong.yang@intel.com \
--cc=dev@dpdk.org \
--cc=jfreimann@redhat.com \
--cc=jianfeng.tan@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=stefanha@redhat.com \
--cc=tiwei.bie@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 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).