On 25-Nov-19 11:32 PM, Thomas Monjalon wrote:
18/11/2019 14:14, Olivier Matz:
On Thu, Nov 14, 2019 at 02:13:06PM +, Anatoly Burakov wrote:
It may not be immediately clear that rte_mem_virt2iova does not actually
check the internal memseg table, and will instead either return VA (in
IOVA as
18/11/2019 14:14, Olivier Matz:
> On Thu, Nov 14, 2019 at 02:13:06PM +, Anatoly Burakov wrote:
> > It may not be immediately clear that rte_mem_virt2iova does not actually
> > check the internal memseg table, and will instead either return VA (in
> > IOVA as VA mode), or will fall back to kerne
On Thu, Nov 14, 2019 at 02:13:06PM +, Anatoly Burakov wrote:
> It may not be immediately clear that rte_mem_virt2iova does not actually
> check the internal memseg table, and will instead either return VA (in
> IOVA as VA mode), or will fall back to kernel page table walk (in IOVA
> as PA mode)
It may not be immediately clear that rte_mem_virt2iova does not actually
check the internal memseg table, and will instead either return VA (in
IOVA as VA mode), or will fall back to kernel page table walk (in IOVA
as PA mode).
Add a note to API documentation indicating the above.
Signed-off-by:
4 matches
Mail list logo
