From: Bill Zhou <dongzhou@nvidia.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
"NBU-Contact-Thomas Monjalon" <thomas@monjalon.net>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>,
"Raslan Darawsheh" <rasland@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix switch port id when representor in bonding
Date: Sun, 15 Nov 2020 12:36:27 +0000 [thread overview]
Message-ID: <DM6PR12MB3033FDA1072ED5B762845865A2E40@DM6PR12MB3033.namprd12.prod.outlook.com> (raw)
In-Reply-To: <78884a9e-d20a-c8c8-aada-8b0a6282724a@intel.com>
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Saturday, November 14, 2020 2:54 AM
> To: Bill Zhou <dongz@mellanox.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>; NBU-Contact-
> Thomas Monjalon <thomas@monjalon.net>
> Cc: stable@dpdk.org; dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>;
> Bill Zhou <dongzhou@nvidia.com>
> Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix switch port id when representor in
> bonding
>
> 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>
Yes, it's fine.
prev parent reply other threads:[~2020-11-15 18:30 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
2020-11-15 12:36 ` Bill Zhou [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=DM6PR12MB3033FDA1072ED5B762845865A2E40@DM6PR12MB3033.namprd12.prod.outlook.com \
--to=dongzhou@nvidia.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--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).