From: chetan bhasin <chetan.bhasin017@gmail.com>
To: matan@mellanox.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Issue with DPDK bonding with Mellanox
Date: Fri, 2 Nov 2018 10:45:56 +0530 [thread overview]
Message-ID: <CACZZ+Y70ECrtnuiYFZKKxMxmPGBRKWTNsH9Z6GZcF=AF5wy1xg@mail.gmail.com> (raw)
In-Reply-To: <AM0PR0502MB4019ADDF986A2BF457D1C3A3D2CE0@AM0PR0502MB4019.eurprd05.prod.outlook.com>
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
>
prev parent reply other threads:[~2018-11-02 5:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 4:53 chetan bhasin
2018-11-01 9:50 ` Matan Azrad
2018-11-02 5:15 ` chetan bhasin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACZZ+Y70ECrtnuiYFZKKxMxmPGBRKWTNsH9Z6GZcF=AF5wy1xg@mail.gmail.com' \
--to=chetan.bhasin017@gmail.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).