DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] Regarding bond and slave driver configuration in DPDK 19.11
@ 2020-08-31 19:02 Nandini Rangaswamy
       [not found] ` <E5190ED0-1CB3-4C62-BC6F-A6761DAD2D4E@juniper.net>
  0 siblings, 1 reply; 2+ messages in thread
From: Nandini Rangaswamy @ 2020-08-31 19:02 UTC (permalink / raw)
  To: dev

Hi ,
I am attempting to setup/configure bond and slave interfaces in DPDK application and it fails in DPDK 19.11.
DPDK daemon is started with the following command line arguments:
--no-daemon --socket-mem 1024 1024 --vdev eth_bond_bond0,mode=4,xmit_policy=l34,socket_id=1,mac=ac:1f:6b:8d:d7:c6,lacp_rate=1,slave=0000:81:00.0,slave=0000:81:00.1

  1.  DPDK application initializes the bond interface first . It sets rx and tx offloads in dev_conf structure as (DEV_RX_OFFLOAD_CHECKSUM | DEV_RX_OFFLOAD_JUMBO_FRAME )

Then the application invokes rte_eth_dev_configure to setup bond. This causes some conditions such as below to fail In DPDK 19.11 :

        if ((dev_conf->rxmode.offloads & dev_info.rx_offload_capa) !=
             dev_conf->rxmode.offloads) {
                        "Ethdev port_id=%u requested
                        Rx offloads 0x%"PRIx64" doesn't match Rx     offloads "
                        "capabilities 0x%"PRIx64" in %s()\n",
                        port_id, dev_conf->rxmode.offloads,
            Return -EINVAL;
        if ((dev_conf->txmode.offloads & dev_info.tx_offload_capa) !=
             dev_conf->txmode.offloads) {
                        "Ethdev port_id=%u requested Tx offloads
                       0x%"PRIx64" doesn't match Tx offloads "
                        "capabilities 0x%"PRIx64" in %s()\n",
                        port_id, dev_conf->txmode.offloads,
             Return -EINVAL;
       Since no slaves are configured yet, the offloads in dev_info structure of bond are set to 0.Hence there is a mismatch between dev_conf structure whose offloads are set in DPDK
       application and dev_info structure in which all the values 0.

         Finally this causes bond and slave driver setup to fail. How can this issue be fixed ?

Thanks and Regards,

Juniper Business Use Only

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-09-30 22:35 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-31 19:02 [dpdk-dev] Regarding bond and slave driver configuration in DPDK 19.11 Nandini Rangaswamy
     [not found] ` <E5190ED0-1CB3-4C62-BC6F-A6761DAD2D4E@juniper.net>
2020-09-29  0:12   ` Robin Fahy

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).