[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY5PR12MB43229840037E730F884C3356DCBD9@BY5PR12MB4322.namprd12.prod.outlook.com>
Date: Mon, 25 Jan 2021 10:57:14 +0000
From: Parav Pandit <parav@...dia.com>
To: Edwin Peer <edwin.peer@...adcom.com>,
Saeed Mahameed <saeed@...nel.org>
CC: "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Jason Gunthorpe <jgg@...dia.com>,
netdev <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
Alexander Duyck <alexander.duyck@...il.com>,
Sridhar Samudrala <sridhar.samudrala@...el.com>,
David Ahern <dsahern@...nel.org>,
Kiran Patil <kiran.patil@...el.com>,
"Jacob Keller" <jacob.e.keller@...el.com>,
"Ertman, David M" <david.m.ertman@...el.com>,
Dan Williams <dan.j.williams@...el.com>,
"Saeed Mahameed" <saeedm@...dia.com>
Subject: RE: [pull request][net-next V10 00/14] Add mlx5 subfunction support
Hi Edwin,
> From: Edwin Peer <edwin.peer@...adcom.com>
> Sent: Monday, January 25, 2021 2:17 AM
>
> On Fri, Jan 22, 2021 at 11:37 AM Saeed Mahameed <saeed@...nel.org>
> wrote:
>
> > For more detailed information about subfunctions please see detailed tag
> > log below.
>
> Apologies for the tardy question out of left field, but I've been
> thinking about this some more. If I recall, the primary motivation for
> this was a means to effectively address more VFs? But, why can't the
> device simply expose more bus numbers?
Several weeks back, Jason already answered this VF scaling question from you at discussion [1].
[1] https://lore.kernel.org/netdev/20201216023928.GG552508@nvidia.com/
Powered by blists - more mailing lists