* [dpdk-dev] [PATCH] doc: fix address type description for IOAT rawdev
@ 2019-10-18 0:01 Xiao Wang
2019-10-17 13:48 ` Bruce Richardson
0 siblings, 1 reply; 3+ messages in thread
From: Xiao Wang @ 2019-10-18 0:01 UTC (permalink / raw)
To: bruce.richardson; +Cc: dev, Xiao Wang
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
--
2.15.1
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [dpdk-dev] [PATCH] doc: fix address type description for IOAT rawdev
2019-10-18 0:01 [dpdk-dev] [PATCH] doc: fix address type description for IOAT rawdev Xiao Wang
@ 2019-10-17 13:48 ` Bruce Richardson
2019-11-15 9:03 ` David Marchand
0 siblings, 1 reply; 3+ messages in thread
From: Bruce Richardson @ 2019-10-17 13:48 UTC (permalink / raw)
To: Xiao Wang; +Cc: dev
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>
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [dpdk-dev] [PATCH] doc: fix address type description for IOAT rawdev
2019-10-17 13:48 ` Bruce Richardson
@ 2019-11-15 9:03 ` David Marchand
0 siblings, 0 replies; 3+ messages in thread
From: David Marchand @ 2019-11-15 9:03 UTC (permalink / raw)
To: Bruce Richardson; +Cc: Xiao Wang, dev
On Thu, Oct 17, 2019 at 3:48 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
> 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")
Cc: stable@dpdk.org
> >
> > Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, thanks.
--
David Marchand
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-11-15 9:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-18 0:01 [dpdk-dev] [PATCH] doc: fix address type description for IOAT rawdev Xiao Wang
2019-10-17 13:48 ` Bruce Richardson
2019-11-15 9:03 ` David Marchand
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).