DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Bill Zhou <dongz@mellanox.com>,
	viacheslavo@nvidia.com, matan@nvidia.com,
	 Thomas Monjalon <thomas@monjalon.net>
Cc: stable@dpdk.org, dev@dpdk.org, rasland@nvidia.com,
	Bill Zhou <dongzhou@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix switch port id when representor in bonding
Date: Fri, 13 Nov 2020 18:54:06 +0000
Message-ID: <78884a9e-d20a-c8c8-aada-8b0a6282724a@intel.com> (raw)
In-Reply-To: <1604469895-418435-1-git-send-email-dongz@mellanox.com>

On 11/4/2020 6:04 AM, Bill Zhou wrote:
> From: Bill Zhou <dongzhou@nvidia.com>
> In the bonding configurations the port switch id for representors
> was composed of pf index in bonding as the 1 msb and the representor's
> index as the remaining 15 lsbs. The special corner case for the host
> PF representor on BF setups with representor id 0xFFFF was missed as well.
> The new switch port id consists of 4 msbs for the pf bonding index and
> the remaining 12 lsbs for the representor index. The switch port id ranges
> for each type of representors are as follows:
> Uplink representor(AKA master): 0xFFFF
> Host PF representor: 0x<pf_bond>FFF
> VF representor: 0x<pf_bond>[0-FFE]
> Fixes: bee57a0a3565 ("net/mlx5: update switch port id in bonding configuration")
> Cc: stable@dpdk.org
> Signed-off-by: Bill Zhou <dongzhou@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Sign off tag is updated as following in the next-net, to keep consistent to 
previously used name:
  Signed-off-by: Dong Zhou <dongzhou@nvidia.com>

  parent reply	other threads:[~2020-11-13 18:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04  6:04 Bill Zhou
2020-11-08  9:49 ` Raslan Darawsheh
2020-11-13 18:54 ` Ferruh Yigit [this message]
2020-11-15 12:36   ` Bill Zhou

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=78884a9e-d20a-c8c8-aada-8b0a6282724a@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=dongz@mellanox.com \
    --cc=dongzhou@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git