> -----Original Message----- > From: Jiri Pirko <jiri@xxxxxxxxxxx> > Sent: Friday, November 8, 2019 3:51 AM > To: Parav Pandit <parav@xxxxxxxxxxxx> > Cc: alex.williamson@xxxxxxxxxx; davem@xxxxxxxxxxxxx; > kvm@xxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx; Saeed Mahameed > <saeedm@xxxxxxxxxxxx>; kwankhede@xxxxxxxxxx; leon@xxxxxxxxxx; > cohuck@xxxxxxxxxx; Jiri Pirko <jiri@xxxxxxxxxxxx>; linux- > rdma@xxxxxxxxxxxxxxx > Subject: Re: [PATCH net-next 01/19] net/mlx5: E-switch, Move devlink port > close to eswitch port > > Thu, Nov 07, 2019 at 05:08:16PM CET, parav@xxxxxxxxxxxx wrote: > >Currently devlink ports are tied to netdev representor. > > > >mlx5_vport structure is better container of e-switch vport compare to > >mlx5e_rep_priv. > >This enables to extend mlx5_vport easily for mdev flavour. > > > >Hence, move devlink_port from netdev representor to mlx5_vport. > > > >Reviewed-by: Saeed Mahameed <saeedm@xxxxxxxxxxxx> > >Signed-off-by: Parav Pandit <parav@xxxxxxxxxxxx> > > Since this patchset has 19 patches, which is quite a lot, I suggest to push out > some preparation patches (like this one) to a separate patchset that would > be sent in prior to this one. Some of us have been doing that for a while now, that made it to 19. :-) We can also take out 5-6 patches of mdev as pre-series, if Alex and others are fine. Please review/ack this patch, so that I can queue via usual Saeed net-next tree which are already reviewed, and this series depends on that esw internal refactor.
