From: Raslan Darawsheh <rasland@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix device scan within switch domain
Date: Tue, 8 Oct 2019 09:35:02 +0000 [thread overview]
Message-ID: <DB3PR0502MB3964206535F89E586C527D9FC29A0@DB3PR0502MB3964.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1570456579-5075-1-git-send-email-viacheslavo@mellanox.com>
Hi,
> -----Original Message-----
> From: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> Sent: Monday, October 7, 2019 4:56 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@mellanox.com>; Raslan Darawsheh
> <rasland@mellanox.com>
> Subject: [PATCH] net/mlx5: fix device scan within switch domain
>
> In LAG configuration the devices in the same switch domain might be
> spawned on the base of different PCI devices, so we should check all devices
> backed by mlx5 PMD whether they belong to specified switch domain. When
> the new devices are being created it is not possible to detect whether the
> sibling devices created in the current probe() loop belong to the driver, driver
> field is not filled yet (it will be done on returned success of current probe()).
> This patch updates the device scanning, allowing extra match on current
> backing PCI device, is being used to create siblings.
>
> Fixes: 9f4a56d68966 ("net/mlx5: extend switch domain searching range")
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2019-10-08 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 13:56 Viacheslav Ovsiienko
2019-10-08 9:35 ` Raslan Darawsheh [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=DB3PR0502MB3964206535F89E586C527D9FC29A0@DB3PR0502MB3964.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=viacheslavo@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).