[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201219094313.27c3d383@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Sat, 19 Dec 2020 09:43:13 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Parav Pandit <parav@...dia.com>
Cc: Saeed Mahameed <saeed@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Jason Gunthorpe <jgg@...dia.com>,
Leon Romanovsky <leonro@...dia.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
David Ahern <dsahern@...nel.org>,
Jacob Keller <jacob.e.keller@...el.com>,
"Sridhar Samudrala" <sridhar.samudrala@...el.com>,
"david.m.ertman@...el.com" <david.m.ertman@...el.com>,
"dan.j.williams@...el.com" <dan.j.williams@...el.com>,
"kiran.patil@...el.com" <kiran.patil@...el.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
Vu Pham <vuhuong@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>
Subject: Re: [net-next v5 07/15] net/mlx5: SF, Add auxiliary device support
On Sat, 19 Dec 2020 04:53:45 +0000 Parav Pandit wrote:
> > Why can't the SF ID match aux dev ID?
> Auxiliary bus holds the SFs of multiple PFs.
I see it now. Very unfortunate :(
> SF ID can be same for SFs from multiple PFs. Encoding PCI address in SF auxiliary device name doesn't do good.
> So SF ID attribute of device is more appropriate.
Powered by blists - more mailing lists