[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY5PR12MB432234DF4437C0FACBB26277DCC20@BY5PR12MB4322.namprd12.prod.outlook.com>
Date: Sat, 19 Dec 2020 04:43:00 +0000
From: Parav Pandit <parav@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>, Saeed Mahameed <saeed@...nel.org>
CC: "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>,
Jiri Pirko <jiri@...dia.com>, Vu Pham <vuhuong@...dia.com>
Subject: RE: [net-next v5 03/15] devlink: Introduce PCI SF port flavour and
port attribute
> From: Jakub Kicinski <kuba@...nel.org>
> Sent: Saturday, December 19, 2020 1:18 AM
> So the SF is always created from the eswitch controller side?
> How does the host side look?
>
Host side creates the auxiliary device for the SF.
$ ls -l /sys/bus/auxiliary/devices/
mlx5_core.sf.4 -> ../../../devices/pci0000:00/0000:00:03.0/0000:06:00.0/mlx5_core.sf.4
> I really think that for ease of merging this we should leave the remote
> controller out at the beginning - only allow local creation.
>
Alright. I will drop remote controller attribute of SF in this patchset.
Powered by blists - more mailing lists