I see. This didn't happen on our setups here since we tests with
newer cards (ConnectX2/3/3-pro).
For ConnectX1 (A0) and this firmware that you are using smells
like something goes wrong. If possible, I would change to newish
card.
No problem with that. My journey up to here was hard but very
On 05/11/2013 10:25, Markus Stockhausen wrote:
Are the TCP Ids in an TSO setup generated through firmware or in the software
stack?
in HW
And if in firmware: How does the card know how to increase them? I would expect
that it only works with IB packets
and does not know of the IP
On Tue, Nov 05, 2013 at 10:48:10AM +0200, Erez Shitrit wrote:
so, to summarize:
The HW does the work (truncates the big ip packet to series of ip
packets, each with the relevant mtu size and increases the ip-id for
each)
The FW enables that work on the HW
the FW in A0 card doesn't enable
so, to summarize:
The HW does the work (truncates the big ip packet to series of ip
packets, each with the relevant mtu size and increases the ip-id for
each)
The FW enables that work on the HW
the FW in A0 card doesn't enable that option for the HW.
Sounds like this bug causes a
