Re: [PATCH v3 1/5] build: clarify configuration without IOVA field in mbuf

2023-03-16 Thread Thomas Monjalon
15/03/2023 02:56, fengchengwen: > On 2023/3/14 22:29, Thomas Monjalon wrote: > > The impact of the option "enable_iova_as_pa" is explained for users. > > > > Also the code flag "RTE_IOVA_AS_PA" is renamed as "RTE_IOVA_IN_MBUF" > > in order to be more accurate (IOVA mode is decided at runtime), > >

Re: [PATCH v3 1/5] build: clarify configuration without IOVA field in mbuf

2023-03-14 Thread fengchengwen
Acked-by: Chengwen Feng On 2023/3/14 22:29, Thomas Monjalon wrote: > The impact of the option "enable_iova_as_pa" is explained for users. > > Also the code flag "RTE_IOVA_AS_PA" is renamed as "RTE_IOVA_IN_MBUF" > in order to be more accurate (IOVA mode is decided at runtime), > and more readable

[PATCH v3 1/5] build: clarify configuration without IOVA field in mbuf

2023-03-14 Thread Thomas Monjalon
The impact of the option "enable_iova_as_pa" is explained for users. Also the code flag "RTE_IOVA_AS_PA" is renamed as "RTE_IOVA_IN_MBUF" in order to be more accurate (IOVA mode is decided at runtime), and more readable in the code. Similarly the drivers are using the variable "require_iova_in_mb