From: Jiayu Hu <jiayu.hu@intel.com>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com, thomas@monjalon.net,
zhihong.wang@intel.com, Jiayu Hu <jiayu.hu@intel.com>
Subject: [dpdk-dev] [PATCH v2] doc: add vhost-user live migration features to release notes
Date: Fri, 9 Feb 2018 15:47:24 +0800 [thread overview]
Message-ID: <1518162444-99915-1-git-send-email-jiayu.hu@intel.com> (raw)
In-Reply-To: <1518160389-82580-1-git-send-email-jiayu.hu@intel.com>
Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
---
change in v2:
- add VIRTIO_F_ANY_LAYOUT feature
doc/guides/rel_notes/release_18_02.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/doc/guides/rel_notes/release_18_02.rst b/doc/guides/rel_notes/release_18_02.rst
index c42a1d6..1d31329 100644
--- a/doc/guides/rel_notes/release_18_02.rst
+++ b/doc/guides/rel_notes/release_18_02.rst
@@ -230,6 +230,17 @@ New Features
current build system using ``make``. For instructions on how to do a DPDK build
using the new system, see the instructions in ``doc/build-sdk-meson.txt``.
+* **Add feature supports for live migration from vhost-net to vhost-user.**
+
+ To make live migration from vhost-net to vhost-user possible, added
+ feature supports for vhost-user. The features include:
+
+ * VIRTIO_F_ANY_LAYOUT
+ * VIRTIO_F_EVENT_IDX
+ * VIRTIO_NET_F_GUEST_ECN, VIRTIO_NET_F_HOST_ECN
+ * VIRTIO_NET_F_GUEST_UFO, VIRTIO_NET_F_HOST_UFO
+ * VIRTIO_NET_F_GSO
+
.. note::
This new build system support is incomplete at this point and is added
--
2.7.4
next prev parent reply other threads:[~2018-02-09 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 7:13 [dpdk-dev] [PATCH] " Jiayu Hu
2018-02-09 7:47 ` Jiayu Hu [this message]
2018-02-09 9:57 ` [dpdk-dev] [PATCH v2] " Mcnamara, John
2018-02-13 23:12 ` Thomas Monjalon
2018-02-09 9:56 ` [dpdk-dev] [PATCH] " Mcnamara, John
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=1518162444-99915-1-git-send-email-jiayu.hu@intel.com \
--to=jiayu.hu@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
--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 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).