From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, tiwei.bie@intel.com, yliu@fridaylinux.org,
jfreimann@redhat.com
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-dev] [RFC 0/2] vhost-user: add VHOST_USER_SET_QUEUE_NUM support
Date: Fri, 12 Jan 2018 16:50:14 +0100 [thread overview]
Message-ID: <20180112155016.8990-1-maxime.coquelin@redhat.com> (raw)
Hi this two-patches series first ensure that no queues will be allocated
while the device is in a running state, and then implements support for
VHOST_USER_SET_QUEUE_NUM vhost-user protocol request.
The goal is to prevent the device to either corrupt some guest memory
when disabling guest notifications, or to be stuck waiting forever for
queues not setup by the guest driver to be initialized, depending on QEMU
version.
One way to reproduce these kind of issues is to start a Windows guest with
setting more queue pairs in QEMU cmdline than vcpus.
I tagged this series as RFC, because the QEMU part [0], which contains
the spec update isn't acked yet.
[0]: http://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg02648.html
Maxime Coquelin (2):
vhost-user: don't allocate new queue once device is running
vhost-user: add support for VHOST_USER_SET_QUEUE_NUM
lib/librte_vhost/vhost_user.c | 50 ++++++++++++++++++++++++++++++++++++++++---
lib/librte_vhost/vhost_user.h | 5 ++++-
2 files changed, 51 insertions(+), 4 deletions(-)
--
2.14.3
next reply other threads:[~2018-01-12 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 15:50 Maxime Coquelin [this message]
2018-01-12 15:50 ` [dpdk-dev] [RFC 1/2] vhost-user: don't allocate new queue once device is running Maxime Coquelin
2018-01-12 15:50 ` [dpdk-dev] [RFC 2/2] vhost-user: add support for VHOST_USER_SET_QUEUE_NUM 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=20180112155016.8990-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=jfreimann@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=yliu@fridaylinux.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).