On Fri, Jun 18, 2010 at 08:42:38AM -0500, Mike Heinz wrote: > First addressing Roland's comment, there are in fact TCP socket > options which control how much buffering is done in the kernel and > hence control message size and segmentation points for TCP. Those > options allow the careful balance of window size, kernel memory > space and TCP performance to be tuned, the defaults for these > options tend to be relatively small. This is possible for TCP since > the protocol is defined at the application level as a byte stream > protocol, hence it is up to the TCP stack to decide the proper > segmentation points and windowing. Applications must be written to > assume a recv() could return only part of a corresponding send() and > could be at any arbitrary byte boundary.
Umh, dumb question.. Why not just add byte-stream like APIs to the kernel interface for RMPP? Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
