From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Red Hat DPDK roadmap for v20.08
Date: Fri, 15 May 2020 15:37:57 +0200 [thread overview]
Message-ID: <e94c5843-6cd2-4849-2ee8-06e5a8dc6f66@redhat.com> (raw)
General:
--------
- Add API to register external threads
Vhost-user library:
-------------------
- Advertise REPLY_ACK protocol feature unconditionally
* Previously depending on RTE_VHOST_USER_IOMMU_SUPPORT registration
flag
* REPLY_ACK is necessary to ensure proper Vhost-user master/slave
synchronization
* Compatibility with old Qemu versions (v2.7 to v2.9.0) will be broken
when multi-queue enabled. These old Qemu versions have not been
maintained for years both upstream and in major distributions
- Add support for SET_STATUS protocol feature
- Rework vDPA API for better integration in DPDK class model
* Target is to remove experimental tag in v20.11
Virtio PMD:
-----------
- Add support for GET/SET_PROTOCOL_FEATURES protocol requests to
Virtio-user PMD
- Add support for REPLY_ACK protocol feature to Virtio-user PMD
- Add support for SET_STATUS protocol request to Virtio-user PMD
reply other threads:[~2020-05-15 13:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e94c5843-6cd2-4849-2ee8-06e5a8dc6f66@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.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).