DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Xuan Ding <xuan.ding@intel.com>, chenbo.xia@intel.com
Cc: dev@dpdk.org, jiayu.hu@intel.com, yinan.wang@intel.com,
	xingguang.he@intel.com
Subject: Re: [PATCH] doc: update recommended IOVA mode for async vhost
Date: Mon, 31 Jan 2022 09:41:26 +0100	[thread overview]
Message-ID: <70ccecb1-06b6-aa67-a1a1-7c944b80f38b@redhat.com> (raw)
In-Reply-To: <20211122084948.39382-1-xuan.ding@intel.com>



On 11/22/21 09:49, Xuan Ding wrote:
> DPDK 21.11 adds vfio support for DMA device in vhost. This patch
> updates recommended IOVA mode in async datapath.
> 
> Signed-off-by: Xuan Ding <xuan.ding@intel.com>
> ---
>   doc/guides/prog_guide/vhost_lib.rst | 9 +++++++++
>   1 file changed, 9 insertions(+)
> 
> diff --git a/doc/guides/prog_guide/vhost_lib.rst b/doc/guides/prog_guide/vhost_lib.rst
> index 76f5d303c9..f72ce75909 100644
> --- a/doc/guides/prog_guide/vhost_lib.rst
> +++ b/doc/guides/prog_guide/vhost_lib.rst
> @@ -442,3 +442,12 @@ Finally, a set of device ops is defined for device specific operations:
>   * ``get_notify_area``
>   
>     Called to get the notify area info of the queue.
> +
> +Recommended IOVA mode in async datapath
> +---------------------------------------
> +
> +When DMA devices are bound to vfio driver, VA mode is recommended.
> +For PA mode, page by page mapping may exceed IOMMU's max capability,
> +better to use 1G guest hugepage.
> +
> +For uio driver, any vfio related error message can be ignored.
> \ No newline at end of file

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime


  reply	other threads:[~2022-01-31  8:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22  8:49 Xuan Ding
2022-01-31  8:41 ` Maxime Coquelin [this message]
2022-02-08 11:10 ` 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=70ccecb1-06b6-aa67-a1a1-7c944b80f38b@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=jiayu.hu@intel.com \
    --cc=xingguang.he@intel.com \
    --cc=xuan.ding@intel.com \
    --cc=yinan.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).