* [dpdk-dev] Issue with DPDK bonding with Mellanox
@ 2018-11-01 4:53 chetan bhasin
2018-11-01 9:50 ` Matan Azrad
0 siblings, 1 reply; 3+ messages in thread
From: chetan bhasin @ 2018-11-01 4:53 UTC (permalink / raw)
To: dev
Hi,
We are using Dpdk 17.11.4 and facing issue in bringing setup with bonding
although without bonding it is working fine.
Your help is much appreciated!
*Command used *
--vdev eth_bond0,mode=1,slave=0000:37:00.0,slave=0000:37:00.1
Error Logs
=============
Oct 31 13:13:07 - INFO - net_mlx5: cannot access device, is mlx5_ib loaded?
Oct 31 13:13:07 - INFO - EAL: Requested device 0000:37:00.1 cannot be used
Oct 31 13:13:07 - INFO - PMD: bond_ethdev_parse_slave_port_kvarg(166) -
Invalid slave port value (0000:37:00.1) specified
Oct 31 13:13:07 - INFO - EAL: Failed to parse slave ports for bonded device
eth_bond0
Oct 31 13:13:07 - INFO - vdev_probe(): failed to initialize eth_bond0
device
Thanks,
Chetan Bhasin
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] Issue with DPDK bonding with Mellanox
2018-11-01 4:53 [dpdk-dev] Issue with DPDK bonding with Mellanox chetan bhasin
@ 2018-11-01 9:50 ` Matan Azrad
2018-11-02 5:15 ` chetan bhasin
0 siblings, 1 reply; 3+ messages in thread
From: Matan Azrad @ 2018-11-01 9:50 UTC (permalink / raw)
To: chetan bhasin, dev
Hi Chetan
From: chetan bhasin
> Hi,
>
> We are using Dpdk 17.11.4 and facing issue in bringing setup with bonding
> although without bonding it is working fine.
>
> Your help is much appreciated!
>
> *Command used *
>
> --vdev eth_bond0,mode=1,slave=0000:37:00.0,slave=0000:37:00.1
>
> Error Logs
> =============
>
> Oct 31 13:13:07 - INFO - net_mlx5: cannot access device, is mlx5_ib loaded?
>
> Oct 31 13:13:07 - INFO - EAL: Requested device 0000:37:00.1 cannot be used
>
> Oct 31 13:13:07 - INFO - PMD: bond_ethdev_parse_slave_port_kvarg(166) -
> Invalid slave port value (0000:37:00.1) specified
>
> Oct 31 13:13:07 - INFO - EAL: Failed to parse slave ports for bonded device
> eth_bond0
>
> Oct 31 13:13:07 - INFO - vdev_probe(): failed to initialize eth_bond0 device
Did you remove the corresponding bonding interface from the kernel?
>
>
> Thanks,
> Chetan Bhasin
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] Issue with DPDK bonding with Mellanox
2018-11-01 9:50 ` Matan Azrad
@ 2018-11-02 5:15 ` chetan bhasin
0 siblings, 0 replies; 3+ messages in thread
From: chetan bhasin @ 2018-11-02 5:15 UTC (permalink / raw)
To: matan; +Cc: dev
Hi Matan,
Thanks for your reply.
I have not removed Mellanox interfaces those were still up in linux domain .
Thanks,
Chetan Bhasin
On Thu, Nov 1, 2018 at 3:20 PM Matan Azrad <matan@mellanox.com> wrote:
> Hi Chetan
>
> From: chetan bhasin
> > Hi,
> >
> > We are using Dpdk 17.11.4 and facing issue in bringing setup with bonding
> > although without bonding it is working fine.
> >
> > Your help is much appreciated!
> >
> > *Command used *
> >
> > --vdev eth_bond0,mode=1,slave=0000:37:00.0,slave=0000:37:00.1
> >
> > Error Logs
> > =============
> >
> > Oct 31 13:13:07 - INFO - net_mlx5: cannot access device, is mlx5_ib
> loaded?
> >
> > Oct 31 13:13:07 - INFO - EAL: Requested device 0000:37:00.1 cannot be
> used
> >
> > Oct 31 13:13:07 - INFO - PMD: bond_ethdev_parse_slave_port_kvarg(166) -
> > Invalid slave port value (0000:37:00.1) specified
> >
> > Oct 31 13:13:07 - INFO - EAL: Failed to parse slave ports for bonded
> device
> > eth_bond0
> >
> > Oct 31 13:13:07 - INFO - vdev_probe(): failed to initialize eth_bond0
> device
>
>
> Did you remove the corresponding bonding interface from the kernel?
>
> >
> >
> > Thanks,
> > Chetan Bhasin
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-11-02 5:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-11-01 4:53 [dpdk-dev] Issue with DPDK bonding with Mellanox chetan bhasin
2018-11-01 9:50 ` Matan Azrad
2018-11-02 5:15 ` chetan bhasin
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).