Applications that use this qp type should build the whole packet,
including link level headers when sending. On the receive side, the
HW isn't expected to strip any headers. The new qp type designated
usage is from user-space in Ethernet environments, e.g by applications
that do TCP/IP offloading.
> Applications that use this qp type should build the whole packet,
> including link level headers when sending. On the receive side, the
> HW isn't expected to strip any headers. The new qp type designated
> usage is from user-space in Ethernet environments, e.g by applications
> that do TCP/IP of
On Thu, Jan 19, 2012 at 3:28 AM, Hefty, Sean wrote:
>> Applications that use this qp type should build the whole packet,
>> including link level headers when sending. On the receive side, the
>> HW isn't expected to strip any headers. The new qp type designated
>> usage is from user-space in Ether
On Thu, 16 Feb 2012, Or Gerlitz wrote:
> Also here, Sean provided his reviewed-by signature, people (CCed
> Christoph and others) keep asking me about this patch set and I didn't
> get any feedback from you.
I sure would like to see this merged for 3.4
--
To unsubscribe from this list: send the
On 2/16/2012 5:27 PM, Christoph Lameter wrote:
On Thu, 16 Feb 2012, Or Gerlitz wrote:
Also here, Sean provided his reviewed-by signature, people (CCed Christoph and
others) keep asking me about this patch set and I didn't get any feedback from
you.
I sure would like to see this merged for 3
On Mon, 12 Mar 2012, Or Gerlitz wrote:
> Same here, I submitted the patches ~two months ago and haven't heard from you,
> I would be happy to see this going into 3.4 and if fixes/changes are needed
> please let me know as soon as possible so I will do them.
I can confirm that the patches in OFED
Thanks, applied at long last.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
