DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Gregory Etelson <getelson@nvidia.com>
Cc: dev@dpdk.org, matan@nvidia.com, rasland@nvidia.com,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Xueming Li <xuemingl@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix port domain_id initialization
Date: Tue, 03 Aug 2021 14:34:41 +0200	[thread overview]
Message-ID: <1678891.g4SDaZsxXZ@thomas> (raw)
In-Reply-To: <20210802145524.3248-1-getelson@nvidia.com>

Title proposal:
net/mlx5: fix port initialization of switch domain

02/08/2021 16:55, Gregory Etelson:
> All active ports that belong to the same E-switch share domain_id
> value.
> Port initialization procedure searches through a database for existing
> port with matching properties. New domain_id allocated if match was
> not located. Otherwise, new port inherits existing domain_id.
> 
> Port initialization did not pass enough info to search procedure to
> find existing matches. Therefore, each port was created with a private
> domain_id value. As the result, port_id flow action failed because it
> could not match ports in a rule to E-switch.
> 
> The patch adds dpdk_dev with port properties to device search.
> 
> Fixes: 56bb3c84e982 ("net/mlx5: reduce PCI dependency")
> 
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Applied, thanks.



      reply	other threads:[~2021-08-03 12:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 14:55 Gregory Etelson
2021-08-03 12:34 ` 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=1678891.g4SDaZsxXZ@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=getelson@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=viacheslavo@nvidia.com \
    --cc=xuemingl@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).