From: Xiao Wang <xiao.w.wang@intel.com>
To: maxime.coquelin@redhat.com
Cc: dev@dpdk.org, tiwei.bie@intel.com, Xiao Wang <xiao.w.wang@intel.com>
Subject: [PATCH 18.05-RC3 0/2] net/virtio-user: support memory hotplug
Date: Tue, 8 May 2018 15:10:43 +0800 [thread overview]
Message-ID: <20180508071045.105475-1-xiao.w.wang@intel.com> (raw)
This patch set has dependency on http://dpdk.org/dev/patchwork/patch/39283/
("mem: add argument to mem event callbacks").
When memory is hot-added or hot-removed, the virtio-user driver has to
notify the vhost-user backend with sending a VHOST_USER_SET_MEM_TABLE
request with the new memory map as payload. This patch set registers
a mem_event callback to help on that.
Considering some older vhost-user implementation doesn't support runtime
memory table change, e.g. DPDK 16.11, we have to pause queues explicitly
in the callback routine:
1. disable all the active queues
2. update memory table to vhost
3. resume all the previous active queues
Maxime Coquelin (2):
vhost: retranslate vring addr when memory table changes
net/virtio-user: support memory hotplug
drivers/net/virtio/virtio_user/virtio_user_dev.c | 53 +++++++++++++++++++++++-
drivers/net/virtio/virtio_user/virtio_user_dev.h | 2 +
lib/librte_vhost/vhost_user.c | 24 ++++++++++-
3 files changed, 76 insertions(+), 3 deletions(-)
--
2.15.1
next reply other threads:[~2018-05-08 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 7:10 Xiao Wang [this message]
2018-05-08 7:10 ` [PATCH 18.05-RC3 1/2] vhost: retranslate vring addr when memory table changes Xiao Wang
2018-05-08 7:10 ` [PATCH 18.05-RC3 2/2] net/virtio-user: support memory hotplug Xiao Wang
2018-05-14 8:29 ` Burakov, Anatoly
2018-05-09 11:30 ` [PATCH 18.05-RC3 0/2] " Ferruh Yigit
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=20180508071045.105475-1-xiao.w.wang@intel.com \
--to=xiao.w.wang@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@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 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.