> > > How close is TCP_NOPUSH to behaving identically to TCP_CORK now?
>
> They have not so much of common.
>
> TCP_NOPUSH enables T/TCP and its presense used to mean that
> T/TCP is possible on this system. Linux headers cannot
> even contain TCP_NOPUSH.
But Tony Finch wrote:
> They are exactly the same.
Alexy, Tony just checked in a change to FreeBSD to make TCP_NOPUSH behave the
same as TCP_CORK.
Tony, are people using the TCP_NOPUSH define as a way to detect
the presence of T/TCP support? In that case, perhaps the right
thing to do to achieve source compatibility would be for FreeBSD
to also define TCP_CORK (and give it TCP_NOPUSH as a value, perhaps).
- Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/