From: David Stevens <[EMAIL PROTECTED]> Date: Tue, 12 Jul 2005 14:16:30 -0700
> In its RFC incantation, it allows for out-of-order delivery of an > arbitrary (but limited) amount of data. The BSD implementation > made it largely unusable by widely distributing something that > didn't compute the offset correctly and only supported 1 byte of > urgent data, but its original form seems pretty close to what you > want, without the receiver having to know where the special > data is in advance. And the BSD-compatible form can be used > in a similar way, with the app doing the buffering instead of the > kernel. > Or am I missing something?? URG is generally unusable. First, it's disuse results in nearly all TCP stacks going to the slow path when it is used. TSO (on output) and the TCP input fast path (on input) are both not used when URG is active. Secondly, if you know where the data is, my MSG_NOCOPY idea takes care of things quite nicely. URG also has the nasty side effect of using signals. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
