>> This is a continuation of the discussions[1] to add mbuf physical address
>> field to
>dynamic field.
>> Previous version was to add PA field to dynamic field area based on the EAL
>IOVA mode option. It was
>> deemed unsafe as some components could still use the PA field without
>checking IOVA
21/09/2022 15:56, Shijith Thotton:
> This is a continuation of the discussions[1] to add mbuf physical address
> field to dynamic field.
> Previous version was to add PA field to dynamic field area based on the EAL
> IOVA mode option. It was
> deemed unsafe as some components could still use the
Hi Olivier,
Thanks for the review.
>On Wed, Sep 21, 2022 at 07:26:16PM +0530, Shijith Thotton wrote:
>> This is a continuation of the discussions[1] to add mbuf physical address
>> field to
>dynamic field.
>> Previous version was to add PA field to dynamic field area based on the EAL
>IOVA mode
Hi Shijith,
On Wed, Sep 21, 2022 at 07:26:16PM +0530, Shijith Thotton wrote:
> This is a continuation of the discussions[1] to add mbuf physical address
> field to dynamic field.
> Previous version was to add PA field to dynamic field area based on the EAL
> IOVA mode option. It was
> deemed uns
>
>This is a continuation of the discussions[1] to add mbuf physical address
>field to
>dynamic field.
>Previous version was to add PA field to dynamic field area based on the EAL
>IOVA
>mode option. It was
>deemed unsafe as some components could still use the PA field without checking
>IOVA mode
This is a continuation of the discussions[1] to add mbuf physical address field
to dynamic field.
Previous version was to add PA field to dynamic field area based on the EAL
IOVA mode option. It was
deemed unsafe as some components could still use the PA field without checking
IOVA mode and ther
6 matches
Mail list logo