[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM0PR05MB4866DF63BB7D80483630F0A9D1EA0@AM0PR05MB4866.eurprd05.prod.outlook.com>
Date: Tue, 18 Jun 2019 10:47:42 +0000
From: Parav Pandit <parav@...lanox.com>
To: Leon Romanovsky <leonro@...lanox.com>,
Saeed Mahameed <saeedm@...lanox.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
Bodong Wang <bodong@...lanox.com>,
Mark Bloch <markb@...lanox.com>
Subject: RE: [PATCH mlx5-next 14/15] {IB, net}/mlx5: E-Switch, Use index of
rep for vport to IB port mapping
Hi Leon,
> -----Original Message-----
> From: Leon Romanovsky
> Sent: Tuesday, June 18, 2019 4:12 PM
> To: Saeed Mahameed <saeedm@...lanox.com>
> Cc: netdev@...r.kernel.org; linux-rdma@...r.kernel.org; Bodong Wang
> <bodong@...lanox.com>; Parav Pandit <parav@...lanox.com>; Mark Bloch
> <markb@...lanox.com>
> Subject: Re: [PATCH mlx5-next 14/15] {IB, net}/mlx5: E-Switch, Use index of rep
> for vport to IB port mapping
>
> On Mon, Jun 17, 2019 at 07:23:37PM +0000, Saeed Mahameed wrote:
> > From: Bodong Wang <bodong@...lanox.com>
> >
> > In the single IB device mode, the mapping between vport number and rep
> > relies on a counter. However for dynamic vport allocation, it is
> > desired to keep consistent map of eswitch vport and IB port.
> >
> > Hence, simplify code to remove the free running counter and instead
> > use the available vport index during load/unload sequence from the
> > eswitch.
> >
> > Signed-off-by: Bodong Wang <bodong@...lanox.com>
> > Suggested-by: Parav Pandit <parav@...lanox.com>
> > Reviewed-by: Parav Pandit <parav@...lanox.com>
>
> We are not adding multiple "*-by" for same user, please choose one.
>
Suggested-by was added by Bodong during our discussion. Later on when I did gerrit +1, RB tag got added.
> Thanks
Powered by blists - more mailing lists