From: Bruce Richardson <bruce.richardson@intel.com>
To: Xiao Wang <xiao.w.wang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: fix address type description for IOAT rawdev
Date: Thu, 17 Oct 2019 14:48:09 +0100 [thread overview]
Message-ID: <20191017134809.GC912@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20191018000147.193134-1-xiao.w.wang@intel.com>
On Thu, Oct 17, 2019 at 08:01:47PM -0400, Xiao Wang wrote:
> Align the description to what the code snippet shows.
>
> Fixes: 0a92e63fc4cd ("raw/ioat: add local API to perform copies")
>
> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
> ---
> doc/guides/rawdevs/ioat.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/guides/rawdevs/ioat.rst b/doc/guides/rawdevs/ioat.rst
> index 607cb5a86..d0eee5e23 100644
> --- a/doc/guides/rawdevs/ioat.rst
> +++ b/doc/guides/rawdevs/ioat.rst
> @@ -160,7 +160,7 @@ the application calls ``rte_ioat_completed_copies()``.
>
> The ``rte_ioat_enqueue_copy()`` function enqueues a single copy to the
> device ring for copying at a later point. The parameters to that function
> -include the physical addresses of both the source and destination buffers,
> +include the IOVA addresses of both the source and destination buffers,
> as well as two "handles" to be returned to the user when the copy is
> completed. These handles can be arbitrary values, but two are provided so
> that the library can track handles for both source and destination on
> --
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2019-10-17 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 0:01 Xiao Wang
2019-10-17 13:48 ` Bruce Richardson [this message]
2019-11-15 9:03 ` David Marchand
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=20191017134809.GC912@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=xiao.w.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).