RE: [PATCH V1 for-next 1/2] IB/core: Report LSO capabilities when querying device

["Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>]

> 
> > We need to decide as a community what we want to do here, because this
> > uncertain process is getting tiring for everyone.
> 
> Agree greatly
> 
> > The Collab Summit discussions ended with a general consensus that some
> > things would go to the driver-specific channel, while hardware
> > behavior related to the common uAPI would go through at least a
> > multi-vendor sign off process - like IBTA.
> 
> I agree with this approach.
> 
> > We didn't talk about how to expose them to apps in userspace once they
> > were exposed through the kernel.
> 
> I think this will end up being vendor specific, and I'm not sure each vendor
knows
> what they want to do.
> 
> > It is pretty obvious the current 'process' isn't working. This new
> > idea that the common uAPI should just be a union of every vendor's
> > unique hardware ideas has not resulted in patches being merged any
> > faster; and I think the quality of the API is not as good now..
> 
> IMO, crafting a common API means a higher level of abstraction.  The lower the
> API, the more it needs to be driver specific.  I prefer a method that: allows
vendors
> to stay out of each other's way, and quickly allows vendors to export their
features
> to user space.  Either of these options can work for that.  I don't see that a
low-
> level, common API is suitable.

Hey all,

I've been trying to follow this thread, and there has been comments that other
device owners should speak up.  But I'm not sure what LSO would do for an iWARP
RC QP connection.  Can someone give me a quick summary?  

Because as it stands now, a ~4GB send can be posted in 1 work request, and FW/HW
(in the iWARP DDP layer) deals with segmenting it based on the MTU for the
interface, and then assembling it to deliver as a single RECV completion at the
peer.  What would LSO do beyond this?
 
Sorry for the dumb question.

Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html