> > On Tue, Jan 23, 2018 at 11:42:20AM -0600, Steve Wise wrote: > > > Since the iwarp protocols run on top of TCP/IP, there is always the case > > that some middle box resegments tcp segments differently, so a good iwarp > HW > > implementation should deal with funny alignments, partial iWARP PDUs > > arriving, etc. But the RFCs, as I read them, want implementations to try > > "really hard" to avoid spanning an iWARP PDU across many TCP segments. > And > > I think siw should do the same, by default. > > But Bernard just said siw doesn't interoperate in certain cases > because of this - so that sounds like more than 'try really hard' ?? > > Or is that an overstatement and it just makes the rx side slower if > segmentation is not optimal? Creating 64K iWARP PDUs causes interoperability problems. If siw builds iWARP PDUs that fit within the TCP wire MSS, then these problems are avoided, and siw becomes more spec compliant. If the iWARP PDUs are built this way, then nothing the tcp stack does will cause problems other than slow down things. -- 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
