From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Jiayu Hu <jiayu.hu@intel.com>
Cc: dev@dpdk.org, maxime.coquelin@redhat.com, zhihong.wang@intel.com
Subject: Re: [dpdk-dev] [PATCH 4/4] doc: add I/OAT acceleration support for vhost-user PMD
Date: Tue, 17 Mar 2020 14:36:56 +0800 [thread overview]
Message-ID: <20200317063656.GA51165@intel.com> (raw)
In-Reply-To: <1584436885-18651-5-git-send-email-jiayu.hu@intel.com>
Hi, Jiayu
DPDK convention prefers to append the doc update with the feature patch, and
update the release note in the same patch as well.
Thanks,
Xiaolong
On 03/17, Jiayu Hu wrote:
>Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
>---
> doc/guides/nics/vhost.rst | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
>diff --git a/doc/guides/nics/vhost.rst b/doc/guides/nics/vhost.rst
>index 912f4bd..f0d9520 100644
>--- a/doc/guides/nics/vhost.rst
>+++ b/doc/guides/nics/vhost.rst
>@@ -25,6 +25,15 @@ Currently, the vhost PMD provides the basic functionality of packet reception, t
>
> * Don't need to stop RX/TX, when the user wants to stop a guest or a virtio-net driver on guest.
>
>+* It supports to offload large data movement in Tx operations from the
>+ CPU to the I/OAT device for every queue. Note that I/OAT acceleration
>+ is just enabled for split rings. In addition, a queue can only use one
>+ I/OAT device, and I/OAT devices cannot be shared among vhost ports and
>+ queues. That is, an I/OAT device can only be used by one queue at a
>+ time. Moreover, users cannot enable I/OAT acceleration, if iommu or
>+ postcopy live-migration is enabled; when enabling I/OAT acceleration
>+ for a queue, Rx interrupt is not supported.
>+
> Vhost PMD arguments
> -------------------
>
>@@ -54,6 +63,11 @@ The user can specify below arguments in `--vdev` option.
> It is used to enable tso support in vhost library.
> (Default: 0 (disabled))
>
>+#. ``dmas``:
>+
>+ It is used to specify DMA engines used to accelerate data movement
>+ in Tx operations for queues.
>+
> Vhost PMD event handling
> ------------------------
>
>--
>2.7.4
>
next prev parent reply other threads:[~2020-03-17 6:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 9:21 [dpdk-dev] [PATCH 0/4] Support DMA-accelerated Tx operations " Jiayu Hu
2020-03-17 9:21 ` [dpdk-dev] [PATCH 1/4] vhost: populate guest memory for DMA-accelerated vhost-user Jiayu Hu
2020-03-17 9:21 ` [dpdk-dev] [PATCH 2/4] net/vhost: setup vrings for DMA-accelerated datapath Jiayu Hu
2020-03-17 6:29 ` Liu, Yong
2020-03-17 9:35 ` Hu, Jiayu
2020-03-18 1:17 ` Liu, Yong
2020-03-17 9:21 ` [dpdk-dev] [PATCH 3/4] net/vhost: leverage DMA engines to accelerate Tx operations Jiayu Hu
2020-03-17 7:21 ` Liu, Yong
2020-03-17 9:31 ` Hu, Jiayu
2020-03-18 1:22 ` Liu, Yong
2020-03-17 9:21 ` [dpdk-dev] [PATCH 4/4] doc: add I/OAT acceleration support for vhost-user PMD Jiayu Hu
2020-03-17 6:36 ` Ye Xiaolong [this message]
2020-03-17 9:53 ` [dpdk-dev] [PATCH 0/4] Support DMA-accelerated Tx operations " Maxime Coquelin
2020-03-19 7:33 ` Hu, Jiayu
2020-03-19 9:10 ` Maxime Coquelin
2020-03-19 11:47 ` Hu, Jiayu
2020-03-26 7:52 ` Maxime Coquelin
2020-03-26 8:25 ` Hu, Jiayu
2020-03-26 8:47 ` Maxime Coquelin
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=20200317063656.GA51165@intel.com \
--to=xiaolong.ye@intel.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=maxime.coquelin@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).