On Mon, Feb 26, 2018 at 09:19:24PM +0200, Leon Romanovsky wrote:
> On Mon, Feb 26, 2018 at 11:59:02AM -0700, Jason Gunthorpe wrote:
> > On Mon, Feb 26, 2018 at 03:02:22PM +0200, Leon Romanovsky wrote:
> >
> > > +struct mlx4_ib_tso_caps {
> > > + __u32 max_tso; /* Maximum tso payload size in bytes */
> > > + /* Corresponding bit will be set if qp type from
> > > + * 'enum ib_qp_type' is supported.
> > > + */
> > > + __u32 supported_qpts;
> > > +};
> >
> > Where is the user space for this?
>
> provider/mlx5/* directory is full of TSO code, there is no reason to
> believe that we won't update provider/mlx4/* after this patch.
Still want to see the user space side before applying any kernel API
update.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
