| Message ID | 1480346664-132493-1-git-send-email-sugesh.chandran@intel.com |
|---|---|
| State | Superseded |
| Delegated to: | Daniele Di Proietto |
| Headers | show |
On Mon, Nov 28, 2016 at 03:24:24PM +0000, Sugesh Chandran wrote: > Add Rx checksum offloading feature support on DPDK physical ports. By default, > the Rx checksum offloading is enabled if NIC supports. However, > the checksum offloading can be turned OFF either while adding a new DPDK > physical port to OVS or at runtime. > > The rx checksum offloading can be turned off by setting the parameter to > 'false'. For eg: To disable the rx checksum offloading when adding a port, > > 'ovs-vsctl add-port br0 dpdk0 -- \ > set Interface dpdk0 type=dpdk options:rx-checksum-offload=false' > > OR (to disable at run time after port is being added to OVS) > > 'ovs-vsctl set Interface dpdk0 options:rx-checksum-offload=false' > > Similarly to turn ON rx checksum offloading at run time, > > 'ovs-vsctl set Interface dpdk0 options:rx-checksum-offload=true' > > The Tx checksum offloading support is not implemented due to the following > reasons. > > 1) Checksum offloading and vectorization are mutually exclusive in DPDK poll > mode driver. Vector packet processing is turned OFF when checksum offloading > is enabled which causes significant performance drop at Tx side. > > 2) Normally, OVS generates checksum for tunnel packets in software at the > 'tunnel push' operation, where the tunnel headers are created. However > enabling Tx checksum offloading involves, > > *) Mark every packets for tx checksum offloading at 'tunnel_push' and > recirculate. > *) At the time of xmit, validate the same flag and instruct the NIC to do the > checksum calculation. In case NIC doesnt support Tx checksum offloading, > the checksum calculation has to be done in software before sending out the > packets. > > No significant performance improvement noticed with Tx checksum offloading > due to the e overhead of additional validations + non vector packet processing. > In some test scenarios, it introduces performance drop too. > > Rx checksum offloading still offers 8-9% of improvement on VxLAN tunneling > decapsulation even though the SSE vector Rx function is disabled in DPDK poll > mode driver. > > Signed-off-by: Sugesh Chandran <sugesh.chandran@intel.com> > Acked-by: Jesse Gross <jesse@kernel.org> Why would a user want to turn off checksum offloading? The patch and the documentation does not explain why, and it seems strange to offer an optimization that a user would not want to use.
Hi Ben, Regards _Sugesh > -----Original Message----- > From: Ben Pfaff [mailto:blp@ovn.org] > Sent: Monday, December 12, 2016 10:24 PM > To: Chandran, Sugesh <sugesh.chandran@intel.com> > Cc: dev@openvswitch.org; jesse@kernel.org > Subject: Re: [ovs-dev] [PATCH v6] netdev-dpdk: Enable Rx checksum > offloading feature on DPDK physical ports. > > On Mon, Nov 28, 2016 at 03:24:24PM +0000, Sugesh Chandran wrote: > > Add Rx checksum offloading feature support on DPDK physical ports. By > > default, the Rx checksum offloading is enabled if NIC supports. > > However, the checksum offloading can be turned OFF either while adding > > a new DPDK physical port to OVS or at runtime. > > > > The rx checksum offloading can be turned off by setting the parameter > > to 'false'. For eg: To disable the rx checksum offloading when adding > > a port, > > > > 'ovs-vsctl add-port br0 dpdk0 -- \ > > set Interface dpdk0 type=dpdk options:rx-checksum-offload=false' > > > > OR (to disable at run time after port is being added to OVS) > > > > 'ovs-vsctl set Interface dpdk0 options:rx-checksum-offload=false' > > > > Similarly to turn ON rx checksum offloading at run time, > > > > 'ovs-vsctl set Interface dpdk0 options:rx-checksum-offload=true' > > > > The Tx checksum offloading support is not implemented due to the > > following reasons. > > > > 1) Checksum offloading and vectorization are mutually exclusive in > > DPDK poll mode driver. Vector packet processing is turned OFF when > > checksum offloading is enabled which causes significant performance drop > at Tx side. > > > > 2) Normally, OVS generates checksum for tunnel packets in software at > > the 'tunnel push' operation, where the tunnel headers are created. > > However enabling Tx checksum offloading involves, > > > > *) Mark every packets for tx checksum offloading at 'tunnel_push' and > > recirculate. > > *) At the time of xmit, validate the same flag and instruct the NIC to do > the > > checksum calculation. In case NIC doesnt support Tx checksum offloading, > > the checksum calculation has to be done in software before sending out > the > > packets. > > > > No significant performance improvement noticed with Tx checksum > > offloading due to the e overhead of additional validations + non vector > packet processing. > > In some test scenarios, it introduces performance drop too. > > > > Rx checksum offloading still offers 8-9% of improvement on VxLAN > > tunneling decapsulation even though the SSE vector Rx function is > > disabled in DPDK poll mode driver. > > > > Signed-off-by: Sugesh Chandran <sugesh.chandran@intel.com> > > Acked-by: Jesse Gross <jesse@kernel.org> > > Why would a user want to turn off checksum offloading? The patch and the > documentation does not explain why, and it seems strange to offer an > optimization that a user would not want to use. [Sugesh] In DPDK, The vectorization get turned off when checksum offloading is enabled, which impacts the performance of smaller(64 bytes) packet traffic. The performance gain offered by checksum offload alleviates the vectorization impact in tunneling decapsulation. However it is not the case for non tunnel traffic. We also noticed the impact of vectorization is not very significant for larger packets >256 bytes for any type of traffic. Considering all these aspects and according to the previous communications on this patch, we decided to give flexibility to user to turn ON/OFF checksum. So that a user who have only non tunnel traffic(with smaller packets) can turn off the checksum offload to get the same old good performance. By default the checksum offload is in ON state. Do you think this information must be mentioned in the documentation? There are lot of parameters involved in there for a normal user to decide upon the checksum offload ON/OFF. Considering the style of documentation which talks only about the available configuration options and its syntax, do we have to put all these information which may cause confusion? As you mentioned, I can provide these details in the commit message. Do you think it is suffice?
On Tue, Dec 13, 2016 at 10:19:53AM +0000, Chandran, Sugesh wrote: > Hi Ben, > > Regards > _Sugesh > > > -----Original Message----- > > From: Ben Pfaff [mailto:blp@ovn.org] > > Sent: Monday, December 12, 2016 10:24 PM > > To: Chandran, Sugesh <sugesh.chandran@intel.com> > > Cc: dev@openvswitch.org; jesse@kernel.org > > Subject: Re: [ovs-dev] [PATCH v6] netdev-dpdk: Enable Rx checksum > > offloading feature on DPDK physical ports. > > > > On Mon, Nov 28, 2016 at 03:24:24PM +0000, Sugesh Chandran wrote: > > > Add Rx checksum offloading feature support on DPDK physical ports. By > > > default, the Rx checksum offloading is enabled if NIC supports. > > > However, the checksum offloading can be turned OFF either while adding > > > a new DPDK physical port to OVS or at runtime. > > > > > > The rx checksum offloading can be turned off by setting the parameter > > > to 'false'. For eg: To disable the rx checksum offloading when adding > > > a port, > > > > > > 'ovs-vsctl add-port br0 dpdk0 -- \ > > > set Interface dpdk0 type=dpdk options:rx-checksum-offload=false' > > > > > > OR (to disable at run time after port is being added to OVS) > > > > > > 'ovs-vsctl set Interface dpdk0 options:rx-checksum-offload=false' > > > > > > Similarly to turn ON rx checksum offloading at run time, > > > > > > 'ovs-vsctl set Interface dpdk0 options:rx-checksum-offload=true' > > > > > > The Tx checksum offloading support is not implemented due to the > > > following reasons. > > > > > > 1) Checksum offloading and vectorization are mutually exclusive in > > > DPDK poll mode driver. Vector packet processing is turned OFF when > > > checksum offloading is enabled which causes significant performance drop > > at Tx side. > > > > > > 2) Normally, OVS generates checksum for tunnel packets in software at > > > the 'tunnel push' operation, where the tunnel headers are created. > > > However enabling Tx checksum offloading involves, > > > > > > *) Mark every packets for tx checksum offloading at 'tunnel_push' and > > > recirculate. > > > *) At the time of xmit, validate the same flag and instruct the NIC to do > > the > > > checksum calculation. In case NIC doesnt support Tx checksum offloading, > > > the checksum calculation has to be done in software before sending out > > the > > > packets. > > > > > > No significant performance improvement noticed with Tx checksum > > > offloading due to the e overhead of additional validations + non vector > > packet processing. > > > In some test scenarios, it introduces performance drop too. > > > > > > Rx checksum offloading still offers 8-9% of improvement on VxLAN > > > tunneling decapsulation even though the SSE vector Rx function is > > > disabled in DPDK poll mode driver. > > > > > > Signed-off-by: Sugesh Chandran <sugesh.chandran@intel.com> > > > Acked-by: Jesse Gross <jesse@kernel.org> > > > > Why would a user want to turn off checksum offloading? The patch and the > > documentation does not explain why, and it seems strange to offer an > > optimization that a user would not want to use. > [Sugesh] In DPDK, The vectorization get turned off when checksum offloading is enabled, which impacts the > performance of smaller(64 bytes) packet traffic. The performance gain offered by checksum offload alleviates the vectorization impact in > tunneling decapsulation. However it is not the case for non tunnel traffic. We also noticed the impact of vectorization is not very significant for larger packets >256 bytes for any type of traffic. > Considering all these aspects and according to the previous communications on this patch, we decided to give flexibility to user to turn ON/OFF checksum. So that a user who have only non tunnel traffic(with smaller packets) can turn off the checksum offload to get the same old good performance. By default the checksum offload is in ON state. > > Do you think this information must be mentioned in the documentation? There are lot of parameters involved in there for a normal user to decide upon the checksum offload ON/OFF. Considering the style of documentation which talks only about the available configuration options and its syntax, do we have to put all these information which may cause confusion? > As you mentioned, I can provide these details in the commit message. Do you think it is suffice? I think that the documentation should try to explain. Users will not read commit messages.
Regards _Sugesh > -----Original Message----- > From: Ben Pfaff [mailto:blp@ovn.org] > Sent: Tuesday, December 13, 2016 4:29 PM > To: Chandran, Sugesh <sugesh.chandran@intel.com> > Cc: dev@openvswitch.org; jesse@kernel.org > Subject: Re: [ovs-dev] [PATCH v6] netdev-dpdk: Enable Rx checksum > offloading feature on DPDK physical ports. > > On Tue, Dec 13, 2016 at 10:19:53AM +0000, Chandran, Sugesh wrote: > > Hi Ben, > > > > Regards > > _Sugesh > > > > > -----Original Message----- > > > From: Ben Pfaff [mailto:blp@ovn.org] > > > Sent: Monday, December 12, 2016 10:24 PM > > > To: Chandran, Sugesh <sugesh.chandran@intel.com> > > > Cc: dev@openvswitch.org; jesse@kernel.org > > > Subject: Re: [ovs-dev] [PATCH v6] netdev-dpdk: Enable Rx checksum > > > offloading feature on DPDK physical ports. > > > > > > On Mon, Nov 28, 2016 at 03:24:24PM +0000, Sugesh Chandran wrote: > > > > Add Rx checksum offloading feature support on DPDK physical ports. > > > > By default, the Rx checksum offloading is enabled if NIC supports. > > > > However, the checksum offloading can be turned OFF either while > > > > adding a new DPDK physical port to OVS or at runtime. > > > > > > > > The rx checksum offloading can be turned off by setting the > > > > parameter to 'false'. For eg: To disable the rx checksum > > > > offloading when adding a port, > > > > > > > > 'ovs-vsctl add-port br0 dpdk0 -- \ > > > > set Interface dpdk0 type=dpdk options:rx-checksum-offload=false' > > > > > > > > OR (to disable at run time after port is being added to OVS) > > > > > > > > 'ovs-vsctl set Interface dpdk0 options:rx-checksum-offload=false' > > > > > > > > Similarly to turn ON rx checksum offloading at run time, > > > > > > > > 'ovs-vsctl set Interface dpdk0 options:rx-checksum-offload=true' > > > > > > > > The Tx checksum offloading support is not implemented due to the > > > > following reasons. > > > > > > > > 1) Checksum offloading and vectorization are mutually exclusive in > > > > DPDK poll mode driver. Vector packet processing is turned OFF when > > > > checksum offloading is enabled which causes significant > > > > performance drop > > > at Tx side. > > > > > > > > 2) Normally, OVS generates checksum for tunnel packets in software > > > > at the 'tunnel push' operation, where the tunnel headers are created. > > > > However enabling Tx checksum offloading involves, > > > > > > > > *) Mark every packets for tx checksum offloading at 'tunnel_push' and > > > > recirculate. > > > > *) At the time of xmit, validate the same flag and instruct the > > > > NIC to do > > > the > > > > checksum calculation. In case NIC doesnt support Tx checksum > offloading, > > > > the checksum calculation has to be done in software before > > > > sending out > > > the > > > > packets. > > > > > > > > No significant performance improvement noticed with Tx checksum > > > > offloading due to the e overhead of additional validations + non > > > > vector > > > packet processing. > > > > In some test scenarios, it introduces performance drop too. > > > > > > > > Rx checksum offloading still offers 8-9% of improvement on VxLAN > > > > tunneling decapsulation even though the SSE vector Rx function is > > > > disabled in DPDK poll mode driver. > > > > > > > > Signed-off-by: Sugesh Chandran <sugesh.chandran@intel.com> > > > > Acked-by: Jesse Gross <jesse@kernel.org> > > > > > > Why would a user want to turn off checksum offloading? The patch > > > and the documentation does not explain why, and it seems strange to > > > offer an optimization that a user would not want to use. > > [Sugesh] In DPDK, The vectorization get turned off when checksum > > offloading is enabled, which impacts the performance of smaller(64 > > bytes) packet traffic. The performance gain offered by checksum offload > alleviates the vectorization impact in tunneling decapsulation. However it is > not the case for non tunnel traffic. We also noticed the impact of > vectorization is not very significant for larger packets >256 bytes for any type > of traffic. > > Considering all these aspects and according to the previous > communications on this patch, we decided to give flexibility to user to turn > ON/OFF checksum. So that a user who have only non tunnel traffic(with > smaller packets) can turn off the checksum offload to get the same old good > performance. By default the checksum offload is in ON state. > > > > Do you think this information must be mentioned in the documentation? > There are lot of parameters involved in there for a normal user to decide > upon the checksum offload ON/OFF. Considering the style of documentation > which talks only about the available configuration options and its syntax, do > we have to put all these information which may cause confusion? > > As you mentioned, I can provide these details in the commit message. Do > you think it is suffice? > > I think that the documentation should try to explain. Users will not read > commit messages. [Sugesh] Ok, I will send out next version of patch after updating the documentation with these details.
diff --git a/INSTALL.DPDK-ADVANCED.rst b/INSTALL.DPDK-ADVANCED.rst index 9b2895b..e209ae4 100644 --- a/INSTALL.DPDK-ADVANCED.rst +++ b/INSTALL.DPDK-ADVANCED.rst @@ -922,6 +922,22 @@ largest frame size supported by Fortville NIC using the DPDK i40e driver, but larger frames and other DPDK NIC drivers may be supported. These cases are common for use cases involving East-West traffic only. +Rx Checksum Offload +------------------- + +By default, DPDK physical ports are enabled with Rx checksum offload. Rx +checksum offload can be configured on a DPDK physical port either when adding +or at run time. + +To disable Rx checksum offload when adding a DPDK port dpdk0:: + + $ ovs-vsctl add-port br0 dpdk0 -- set Interface dpdk0 type=dpdk \ + options:rx-checksum-offload=false + +Similarly to disable the Rx checksum offloading on a existing DPDK port dpdk0:: + + $ ovs-vsctl set Interface dpdk0 type=dpdk options:rx-checksum-offload=false + vsperf ------ diff --git a/lib/dp-packet.h b/lib/dp-packet.h index 1469864..d61ec83 100644 --- a/lib/dp-packet.h +++ b/lib/dp-packet.h @@ -598,6 +598,35 @@ dp_packet_rss_invalidate(struct dp_packet *p) #endif } +static inline bool +dp_packet_ip_checksum_valid(struct dp_packet *p) +{ +#ifdef DPDK_NETDEV + return p->mbuf.ol_flags & PKT_RX_IP_CKSUM_GOOD; +#else + return 0; +#endif +} + +static inline bool +dp_packet_l4_checksum_valid(struct dp_packet *p) +{ +#ifdef DPDK_NETDEV + return p->mbuf.ol_flags & PKT_RX_L4_CKSUM_GOOD; +#else + return 0; +#endif +} + +static inline void +reset_dp_packet_checksum_ol_flags(struct dp_packet *p) +{ +#ifdef DPDK_NETDEV + p->mbuf.ol_flags &= ~(PKT_RX_L4_CKSUM_GOOD | PKT_RX_L4_CKSUM_BAD | + PKT_RX_IP_CKSUM_GOOD | PKT_RX_IP_CKSUM_BAD); +#endif +} + enum { NETDEV_MAX_BURST = 32 }; /* Maximum number packets in a batch. */ struct dp_packet_batch { diff --git a/lib/netdev-dpdk.c b/lib/netdev-dpdk.c index 7564ad7..4a46d36 100644 --- a/lib/netdev-dpdk.c +++ b/lib/netdev-dpdk.c @@ -319,6 +319,10 @@ struct ingress_policer { rte_spinlock_t policer_lock; }; +enum dpdk_hw_ol_features { + NETDEV_RX_CHECKSUM_OFFLOAD = 1 << 0, +}; + struct netdev_dpdk { struct netdev up; int port_id; @@ -384,6 +388,10 @@ struct netdev_dpdk { /* DPDK-ETH Flow control */ struct rte_eth_fc_conf fc_conf; + + /* DPDK-ETH hardware offload features, + * from the enum set 'dpdk_hw_ol_features' */ + uint32_t hw_ol_features; }; struct netdev_rxq_dpdk { @@ -633,6 +641,8 @@ dpdk_eth_dev_queue_setup(struct netdev_dpdk *dev, int n_rxq, int n_txq) conf.rxmode.jumbo_frame = 0; conf.rxmode.max_rx_pkt_len = 0; } + conf.rxmode.hw_ip_checksum = (dev->hw_ol_features & + NETDEV_RX_CHECKSUM_OFFLOAD) != 0; /* A device may report more queues than it makes available (this has * been observed for Intel xl710, which reserves some of them for * SRIOV): rte_eth_*_queue_setup will fail if a queue is not @@ -693,6 +703,29 @@ dpdk_eth_dev_queue_setup(struct netdev_dpdk *dev, int n_rxq, int n_txq) } static void +dpdk_eth_checksum_offload_configure(struct netdev_dpdk *dev) + OVS_REQUIRES(dev->mutex) +{ + struct rte_eth_dev_info info; + bool rx_csum_ol_flag = false; + uint32_t rx_chksm_offload_capa = DEV_RX_OFFLOAD_UDP_CKSUM | + DEV_RX_OFFLOAD_TCP_CKSUM | + DEV_RX_OFFLOAD_IPV4_CKSUM; + rte_eth_dev_info_get(dev->port_id, &info); + rx_csum_ol_flag = (dev->hw_ol_features & NETDEV_RX_CHECKSUM_OFFLOAD) != 0; + + if (rx_csum_ol_flag && + (info.rx_offload_capa & rx_chksm_offload_capa) != + rx_chksm_offload_capa) { + VLOG_WARN_ONCE("Failed to enable Rx checksum offload on device %d", + dev->port_id); + dev->hw_ol_features &= ~NETDEV_RX_CHECKSUM_OFFLOAD; + return; + } + netdev_request_reconfigure(&dev->up); +} + +static void dpdk_eth_flow_ctrl_setup(struct netdev_dpdk *dev) OVS_REQUIRES(dev->mutex) { if (rte_eth_dev_flow_ctrl_set(dev->port_id, &dev->fc_conf)) { @@ -851,6 +884,9 @@ netdev_dpdk_init(struct netdev *netdev, unsigned int port_no, /* Initialize the flow control to NULL */ memset(&dev->fc_conf, 0, sizeof dev->fc_conf); + + /* Initilize the hardware offload flags to 0 */ + dev->hw_ol_features = 0; if (type == DPDK_DEV_ETH) { err = dpdk_eth_dev_init(dev); if (err) { @@ -1113,6 +1149,8 @@ netdev_dpdk_set_config(struct netdev *netdev, const struct smap *args) {RTE_FC_NONE, RTE_FC_TX_PAUSE}, {RTE_FC_RX_PAUSE, RTE_FC_FULL } }; + bool rx_chksm_ofld; + bool temp_flag; ovs_mutex_lock(&dev->mutex); @@ -1136,6 +1174,15 @@ netdev_dpdk_set_config(struct netdev *netdev, const struct smap *args) dpdk_eth_flow_ctrl_setup(dev); } + /* Rx checksum offload configuration */ + /* By default the Rx checksum offload is ON */ + rx_chksm_ofld = smap_get_bool(args, "rx-checksum-offload", true); + temp_flag = (dev->hw_ol_features & NETDEV_RX_CHECKSUM_OFFLOAD) + != 0; + if (temp_flag != rx_chksm_ofld) { + dev->hw_ol_features ^= NETDEV_RX_CHECKSUM_OFFLOAD; + dpdk_eth_checksum_offload_configure(dev); + } ovs_mutex_unlock(&dev->mutex); return 0; diff --git a/lib/netdev-native-tnl.c b/lib/netdev-native-tnl.c index ce2582f..c730e72 100644 --- a/lib/netdev-native-tnl.c +++ b/lib/netdev-native-tnl.c @@ -85,9 +85,11 @@ netdev_tnl_ip_extract_tnl_md(struct dp_packet *packet, struct flow_tnl *tnl, ovs_be32 ip_src, ip_dst; - if (csum(ip, IP_IHL(ip->ip_ihl_ver) * 4)) { - VLOG_WARN_RL(&err_rl, "ip packet has invalid checksum"); - return NULL; + if (OVS_UNLIKELY(!dp_packet_ip_checksum_valid(packet))) { + if (csum(ip, IP_IHL(ip->ip_ihl_ver) * 4)) { + VLOG_WARN_RL(&err_rl, "ip packet has invalid checksum"); + return NULL; + } } if (ntohs(ip->ip_tot_len) > l3_size) { @@ -179,18 +181,21 @@ udp_extract_tnl_md(struct dp_packet *packet, struct flow_tnl *tnl, } if (udp->udp_csum) { - uint32_t csum; - if (netdev_tnl_is_header_ipv6(dp_packet_data(packet))) { - csum = packet_csum_pseudoheader6(dp_packet_l3(packet)); - } else { - csum = packet_csum_pseudoheader(dp_packet_l3(packet)); - } - - csum = csum_continue(csum, udp, dp_packet_size(packet) - - ((const unsigned char *)udp - - (const unsigned char *)dp_packet_l2(packet))); - if (csum_finish(csum)) { - return NULL; + if (OVS_UNLIKELY(!dp_packet_l4_checksum_valid(packet))) { + uint32_t csum; + if (netdev_tnl_is_header_ipv6(dp_packet_data(packet))) { + csum = packet_csum_pseudoheader6(dp_packet_l3(packet)); + } else { + csum = packet_csum_pseudoheader(dp_packet_l3(packet)); + } + + csum = csum_continue(csum, udp, dp_packet_size(packet) - + ((const unsigned char *)udp - + (const unsigned char *)dp_packet_l2(packet) + )); + if (csum_finish(csum)) { + return NULL; + } } tnl->flags |= FLOW_TNL_F_CSUM; } diff --git a/lib/netdev.c b/lib/netdev.c index 860781d..f7a1001 100644 --- a/lib/netdev.c +++ b/lib/netdev.c @@ -741,6 +741,10 @@ netdev_pop_header(struct netdev *netdev, struct dp_packet_batch *batch) for (i = 0; i < batch->count; i++) { buffers[i] = netdev->netdev_class->pop_header(buffers[i]); if (buffers[i]) { + /* Reset the checksum offload flags if present, to avoid wrong + * interpretation in the further packet processing when + * recirculated.*/ + reset_dp_packet_checksum_ol_flags(buffers[i]); buffers[n_cnt++] = buffers[i]; } } diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml index b92b7c0..fa82beb 100644 --- a/vswitchd/vswitch.xml +++ b/vswitchd/vswitch.xml @@ -3187,6 +3187,20 @@ </column> </group> + <group title="Rx Checksum Offload Configuration"> + <p> + The checksum validation on the incoming packets are performed on NIC + using Rx checksum offload feature. Implemented only for <code>dpdk + </code>physical interfaces. + </p> + + <column name="options" key="rx-checksum-offload" + type='{"type": "boolean"}'> + Set to <code>false</code> to disble Rx checksum offloading on <code> + dpdk</code>physical ports. By default, Rx checksum offload is enabled. + </column> + </group> + <group title="Common Columns"> The overall purpose of these columns is described under <code>Common Columns</code> at the beginning of this document.