[ovs-dev] [RFC PATCHv2] netdev-dpdk: Enable Rx checksum offloading feature on DPDK physical ports.

Jesse Gross jesse at kernel.org
Mon Aug 22 16:40:47 UTC 2016


On Mon, Aug 22, 2016 at 6:38 AM, Chandran, Sugesh
<sugesh.chandran at intel.com> wrote:
>> -----Original Message-----
>> From: Jesse Gross [mailto:jesse at kernel.org]
>> Sent: Saturday, August 20, 2016 2:07 AM
>> To: Chandran, Sugesh <sugesh.chandran at intel.com>
>> Cc: ovs dev <dev at openvswitch.org>
>> Subject: Re: [RFC PATCHv2] netdev-dpdk: Enable Rx checksum offloading
>> feature on DPDK physical ports.
>> In the future, if DPDK offloads become tunnel aware some of these issues
>> can become quite complicated due to the presence of multiple checksums
>> being offloaded and how that is represented. On the Linux side there was a
>> fair amount of work put into this over the past several years, so it might be
>> worth taking a look at that for some inspiration before the DPDK interfaces
>> get locked down.
> [Sugesh] May be in the future when DPDK starts supporting checksum offload for
> inner packets, Its worth to define it as 'csum_level' with CHECKSUM_UNNECESSARY than defining separate flags
> for every packet type, which is similar to what kernel is doing for tunnel packet checksum offloading. The checksum reset &
> validation logic must take care of this by changing the csum_level value and CHECKSUM_* flag accordingly.
>
>
> However the current DPDK driver only supports IP and L4 checksum offloading using independent flags.
> Will provide the inputs when other checksum offloading features are implementing in DPDK in the future.

Yes, I don't think that there is anything that can be or needs to be
done on the OVS side at this point. The main reason why I mentioned it
is to see if there is anything that we should do on the DPDK API side
now to reduce possible API incompatibilities in the future if changes
are necessary.



More information about the dev mailing list