[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201215165109.27906764@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Tue, 15 Dec 2020 16:51:09 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: 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,
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, dan.j.williams@...el.com,
kiran.patil@...el.com, gregkh@...uxfoundation.org,
Parav Pandit <parav@...dia.com>, Vu Pham <vuhuong@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>
Subject: Re: [net-next v5 11/15] net/mlx5: SF, Add port add delete
functionality
On Tue, 15 Dec 2020 01:03:54 -0800 Saeed Mahameed wrote:
> To handle SF port management outside of the eswitch as independent
> software layer, introduce eswitch notifier APIs so that upper layer who
> wish to support sf port management in switchdev mode can perform its
Could you unpack this? What's the "upper layer" software in this
context?
> task whenever eswitch mode is set to switchdev or before eswitch is
> disabled.
How does SF work if eswich is disabled?
> Initialize sf port table on such eswitch event.
>
> Add SF port add and delete functionality in switchdev mode.
> Destroy all SF ports when eswitch is disabled.
> Expose SF port add and delete to user via devlink commands.
Powered by blists - more mailing lists