From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, ktraynor@redhat.com, ian.stokes@intel.com,
chenbo.xia@intel.com, zhihong.wang@intel.com
Cc: ciara.loftus@intel.com, Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-dev] [PATCH] doc: announce Vhost dequeue zero-copy removal
Date: Mon, 3 Aug 2020 16:55:38 +0200 [thread overview]
Message-ID: <20200803145538.117096-1-maxime.coquelin@redhat.com> (raw)
Vhost-user dequeue zero-copy support will be removed in
20.11. The only known user is OVS where the feature is
still experimental, and has not received any update for
several years. This feature faces reliability issues and
is often conflicting with new features being implemented.
Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
---
Hi, the topic was discussed during OVS-DPDK public meeting
on July 22nd. Ian, if you had time to discuss the topic with
your team and agree with the removal, please ack the patch.
If, not please let me know.
doc/guides/rel_notes/deprecation.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index ea4cfa7a48..a923849419 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -151,3 +151,8 @@ Deprecation Notices
Python 2 support will be completely removed in 20.11.
In 20.08, explicit deprecation warnings will be displayed when running
scripts with Python 2.
+
+* vhost: Vhost-user dequeue zero-copy support will be removed in 20.11. The
+ only known user is OVS where the feature is still experimental, and has not
+ received any update for 2.5 years. This feature faces reliability issues and
+ is often conflicting with new features being implemented.
--
2.26.2
next reply other threads:[~2020-08-03 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 14:55 Maxime Coquelin [this message]
2020-08-04 1:36 ` Xia, Chenbo
2020-08-06 12:12 ` Stokes, Ian
2020-08-07 11:56 ` Loftus, Ciara
2020-08-07 13:00 ` Aaron Conole
2020-08-07 13:56 ` Thomas Monjalon
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=20200803145538.117096-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=ian.stokes@intel.com \
--cc=ktraynor@redhat.com \
--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).