From: Thomas Monjalon <thomas@monjalon.net>
To: chetan bhasin <chetan.bhasin017@gmail.com>
Cc: dev@dpdk.org, david.marchand@redhat.com,
Chas Williams <chas3@att.com>,
gaetan.rivet@6wind.com
Subject: Re: How to use mlx4 as bond
Date: Wed, 27 Mar 2019 01:51:43 +0100 [thread overview]
Message-ID: <3003267.NZbS04Euqv@xps> (raw)
In-Reply-To: <CACZZ+Y7pBGkuc3yczB++xUTORf59BxYmqQPaDUjBovZj8k9sQg@mail.gmail.com>
Hi,
26/03/2019 16:36, chetan bhasin:
> Hi,
>
> I am using DPDK 17.11.4 with a Mellanox ConnectX-3 Pro dual port card, one
> of the features of this card is that both ports have the same PCI address.
> i.e. there are two ports here but only one PCI reported:
>
> # lspci | grep -i mell
> 0a:00.0 Ethernet controller: Mellanox Technologies MT27520 Family
> [ConnectX-3 Pro]
>
> Is there any way to configure DPDK to set up bonding with this card?
> Bonding requires two unique PCI addresses, is there a way to tell DPDK
> about the two interfaces other than via PCI? I am using VPP to interface
> with DPDK and set up the bonding via vdev configuration. Is bonding just
> not possible using the two interfaces on this device?
It is a design mistake to use PCI address to select slave ports for bonding.
It prevents using multi-port devices or non-PCI devices (like vdev).
The solution is to use another format, like the new devargs syntax,
which allows to match more properties (PCI address being one property).
For ConnectX-3 Pro, it will allow to choose ports by MAC address
with this string: "class=eth,mac=00:11:22:33:44:55"
Unfortunately, this solution requires a patch in the bonding PMD
to use RTE_ETH_FOREACH_MATCHING_DEV().
Note that RTE_ETH_FOREACH_MATCHING_DEV supports the old PCI-only syntax.
Would you like to make it a try?
prev parent reply other threads:[~2019-03-27 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 15:36 How to use mlx4 as bond chetan bhasin
2019-03-27 0:51 ` Thomas Monjalon [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=3003267.NZbS04Euqv@xps \
--to=thomas@monjalon.net \
--cc=chas3@att.com \
--cc=chetan.bhasin017@gmail.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.