From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Xiao Wang <xiao.w.wang@intel.com>, maxime.coquelin@redhat.com
Cc: dev@dpdk.org, tiwei.bie@intel.com
Subject: Re: [PATCH 18.05-RC3 2/2] net/virtio-user: support memory hotplug
Date: Mon, 14 May 2018 09:29:46 +0100 [thread overview]
Message-ID: <cbbbcb0b-0f3f-f2b4-c9b8-147d04e9ab3e@intel.com> (raw)
In-Reply-To: <20180508071045.105475-3-xiao.w.wang@intel.com>
On 08-May-18 8:10 AM, Xiao Wang wrote:
> From: Maxime Coquelin <maxime.coquelin@redhat.com>
>
> 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 implements and registers a mem_event callback, it pauses the
> datapath and updates memory regions to vhost in case of hot-add or
> hot-remove event. This memory region update has only to be done when the
> device is already started, so a new status flag is added to the device to
> keep track of the status.
>
> As the device can now be managed by different threads, a mutex is
> introduced to protect against concurrent device configuration.
>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
> ---
Memory part looks OK to me.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-05-14 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 7:10 [PATCH 18.05-RC3 0/2] net/virtio-user: support memory hotplug Xiao Wang
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 [this message]
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=cbbbcb0b-0f3f-f2b4-c9b8-147d04e9ab3e@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=xiao.w.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.