On 2/18/22 7:28 PM, Nithin Kumar Dabilpuram wrote:
On 2/18/22 12:47 AM, Ananyev, Konstantin wrote:
Enable Tx IPv4 checksum offload only when Tx inline crypto is needed.
In other cases such as Tx Inline protocol offload, checksum
computation
is implicitly taken care by HW.
Why is that?
On 2/18/22 12:47 AM, Ananyev, Konstantin wrote:
Enable Tx IPv4 checksum offload only when Tx inline crypto is needed.
In other cases such as Tx Inline protocol offload, checksum computation
is implicitly taken care by HW.
Why is that?
These is two separate HW offload and user has to enable
> >> Enable Tx IPv4 checksum offload only when Tx inline crypto is needed.
> >> In other cases such as Tx Inline protocol offload, checksum computation
> >> is implicitly taken care by HW.
> >
> > Why is that?
> > These is two separate HW offload and user has to enable each of them
> > explicitly
On 2/7/22 3:22 PM, Ananyev, Konstantin wrote:
Enable Tx IPv4 checksum offload only when Tx inline crypto is needed.
In other cases such as Tx Inline protocol offload, checksum computation
is implicitly taken care by HW.
Why is that?
These is two separate HW offload and user has to enable e
> Enable Tx IPv4 checksum offload only when Tx inline crypto is needed.
> In other cases such as Tx Inline protocol offload, checksum computation
> is implicitly taken care by HW.
Why is that?
These is two separate HW offload and user has to enable each of them explicitly.
Also we can TX clear-t
Enable Tx IPv4 checksum offload only when Tx inline crypto is needed.
In other cases such as Tx Inline protocol offload, checksum computation
is implicitly taken care by HW. The advantage of having only necessary
offloads enabled is that Tx burst function can be as light as possible.
Signed-off-by
6 matches
Mail list logo
