patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Michael Baum <michaelba@nvidia.com>, stable@dpdk.org
Cc: Matan Azrad <matan@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [PATCH 20.11] net/mlx5: fix sibling device config check
Date: Mon, 07 Mar 2022 20:17:42 +0000	[thread overview]
Message-ID: <a0cbcf4acd29026cf8ad09243e6f8bd5ae78dc51.camel@debian.org> (raw)
In-Reply-To: <20220307182955.626660-1-michaelba@nvidia.com>

On Mon, 2022-03-07 at 20:29 +0200, Michael Baum wrote:
> [ upstream commit dcbaafdc8f70987c6b610af7d43817b560fb646b ]
> 
> The MLX5 net driver supports "probe again". In probing again, it
> creates a new ethdev under an existing infiniband device context.
> 
> Sibling devices sharing infiniband device context should have compatible
> configurations, so some of the devargs given in the probe again, the
> ones that are mainly relevant to the sharing device context are sent to
> the mlx5_dev_check_sibling_config function which makes sure that they
> compatible its siblings.
> However, the arguments are adjusted according to the capability of the
> device, and the function compares the arguments of the probe again
> before the adjustment with the arguments of the siblings after the
> adjustment. A user who sends the same values to all siblings may fail in
> this comparison if he requested something that the device does not
> support and adjusted.
> 
> This patch moves the call to the mlx5_dev_check_sibling_config function
> after the relevant adjustments.
> 
> Fixes: 92d5dd483450 ("net/mlx5: check sibling device configurations mismatch")
> Fixes: 2d241515ebaf ("net/mlx5: add devarg for extensive metadata support")
> 
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
>  drivers/net/mlx5/linux/mlx5_os.c | 53 +++++++++++++++++---------------
>  1 file changed, 29 insertions(+), 24 deletions(-)

Thanks, applied and pushed.

-- 
Kind regards,
Luca Boccassi

      reply	other threads:[~2022-03-07 20:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 18:29 Michael Baum
2022-03-07 20:17 ` Luca Boccassi [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=a0cbcf4acd29026cf8ad09243e6f8bd5ae78dc51.camel@debian.org \
    --to=bluca@debian.org \
    --cc=matan@nvidia.com \
    --cc=michaelba@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@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;
as well as URLs for NNTP newsgroup(s).