Re: [PATCH rdma-next v1 3/3] RDMA/mlx5: Use restrack allocation PD scheme

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 29, 2019 at 07:11:42PM +0200, Leon Romanovsky wrote:
> On Tue, Jan 29, 2019 at 10:38:35AM -0600, Steve Wise wrote:
> >
> > On 1/29/2019 1:25 AM, Leon Romanovsky wrote:
> > > From: Leon Romanovsky <leonro@xxxxxxxxxxxx>
> > >
> > > Adapt mlx5 to share restrack ID instead of local variable.
> > >
> > > Signed-off-by: Leon Romanovsky <leonro@xxxxxxxxxxxx>
> >
> >
> > Hey Leon, By not doing this for the other drivers, are they loosing some
> > restrack functionality?  Shouldn't all the drivers be changed?
> 
> From functionality point of view, unconverted drivers will work exactly
> as they worked before. The main differences between converted and
> unconverted are:
> 1. Objects which are created by driver won't be visible to user
> through rdmatool.

I want to see the series organized so that all drivers export all core
created objects via netlink.

Follow on driver-specific series like this should only be to make the
ID #'s used in netlink match some kind of useful driver-specific
number, or to remove now duplicate number assignment/tracking code in
drivers.

Jason




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux