Netdev List
 help / color / mirror / Atom feed
From: Tariq Toukan <tariqt@nvidia.com>
To: Peter Morrow <pdmorrow@gmail.com>, Tariq Toukan <tariqt@nvidia.com>
Cc: Leon Romanovsky <leon@kernel.org>,
	Petr Pavlu <petr.pavlu@suse.com>,
	Yishai Hadas <yishaih@nvidia.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S . Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [PATCH net] net/mlx4: always create the eth and ib auxiliary devices
Date: Wed, 28 Oct 2026 09:20:36 +0200	[thread overview]
Message-ID: <90b2aec6-a473-4de1-9334-947e1a02c090@nvidia.com> (raw)
In-Reply-To: <20261020164239.3808903-1-pdmorrow@gmail.com>



On 20/10/2026 19:42, Peter Morrow wrote:
> Since commit 7d22b1cb9d84 ("mlx4: Connect the infiniband part to the
> auxiliary bus"), mlx4_core creates the "ib" auxiliary device only for
> an IB port or a device that advertises IBoE. Before it, each mlx4
> interface was offered every device and decided in its own add callback.
> mlx4_ib_add() accepted Ethernet ports without IBoE and registered them
> for raw packet QPs only.
> 
> ConnectX-3 VFs on Azure have an Ethernet port and no IBoE, so since
> v6.6 they get no RDMA device. DPDK's mlx4 PMD, which needs only raw
> packet QPs, then cannot open them:
> 
>    net_mlx4: cannot access device, is mlx4_ib loaded?
> 
> Restore the old behaviour by creating both auxiliary devices for every
> device and letting mlx4_en and mlx4_ib decide in probe, as their add
> callbacks did. mlx4_ib_probe() returns -ENODEV when there are no usable
> ports, and mlx4_en_probe() binds a device without Ethernet ports but
> creates no netdevs, as mlx4_en_add() did.
> 
> Tested on 6.12.111 on an Azure VM with two ConnectX-3 VFs: each gets an
> eth and an ib auxiliary device, and DPDK attaches both VFs and passes
> traffic through them.
> 
> Fixes: 7d22b1cb9d84 ("mlx4: Connect the infiniband part to the auxiliary bus")
> Closes: https://lore.kernel.org/r/20261014133951.3219055-1-pdmorrow@gmail.com
> Suggested-by: Leon Romanovsky <leon@kernel.org>
> Assisted-by: LLM
> Signed-off-by: Peter Morrow <pdmorrow@gmail.com>
> ---
>   drivers/net/ethernet/mellanox/mlx4/intf.c | 15 ++-------------
>   1 file changed, 2 insertions(+), 13 deletions(-)
> 


Acked-by: Tariq Toukan <tariqt@nvidia.com>


> diff --git a/drivers/net/ethernet/mellanox/mlx4/intf.c b/drivers/net/ethernet/mellanox/mlx4/intf.c
> index 82e467c..31860b4 100644
> --- a/drivers/net/ethernet/mellanox/mlx4/intf.c
> +++ b/drivers/net/ethernet/mellanox/mlx4/intf.c
> @@ -43,23 +43,12 @@ static DEFINE_IDA(mlx4_adev_ida);
>   
>   static bool is_eth_supported(struct mlx4_dev *dev)
>   {
> -	for (int port = 1; port <= dev->caps.num_ports; port++)
> -		if (dev->caps.port_type[port] == MLX4_PORT_TYPE_ETH)
> -			return true;
> -
> -	return false;
> +	return true;
>   }
>   
>   static bool is_ib_supported(struct mlx4_dev *dev)
>   {
> -	for (int port = 1; port <= dev->caps.num_ports; port++)
> -		if (dev->caps.port_type[port] == MLX4_PORT_TYPE_IB)
> -			return true;
> -
> -	if (dev->caps.flags & MLX4_DEV_CAP_FLAG_IBOE)
> -		return true;
> -
> -	return false;
> +	return true;
>   }
>   
>   static const struct mlx4_adev_device {


  parent reply	other threads:[~2026-10-28  7:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 16:42 [PATCH net] net/mlx4: always create the eth and ib auxiliary devices Peter Morrow
2026-10-22 10:19 ` Simon Horman
2026-10-23 14:08   ` Peter Morrow
2026-10-23 16:56     ` Simon Horman
2026-10-23 11:22 ` Daniel Machon
2026-10-27  8:50 ` Paolo Abeni
2026-10-28  7:20 ` Tariq Toukan [this message]
2026-10-28  8:40 ` patchwork-bot+netdevbpf

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=90b2aec6-a473-4de1-9334-947e1a02c090@nvidia.com \
    --to=tariqt@nvidia.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pdmorrow@gmail.com \
    --cc=petr.pavlu@suse.com \
    --cc=regressions@lists.linux.dev \
    --cc=yishaih@nvidia.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