Skip to contentSkip to conversation

TCP_NOPUSH on FreeBSD, TCP_CORK on Linux (was: Is sendfile all that

DISCUSSION Dan Kegel 3 participants 3 messages Feb 8, 2001

lore
Share & tools
lore

Dan Kegel

author
#0 lore raw
Quoted 7 lines · Alexy
Quoted 1 line
Quoted 1 line

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.

Quoted 1 line · But Tony Finch

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 [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#1 lore raw
Quoted 3 lines · Dan Kegel

Tony, are people using the TCP_NOPUSH define as a way to detect the presence of T/TCP support?

No, MSG_EOF is the right way to do that.

Tony.

Signature · 6 lines
f.a.n.finch    [email protected]    [email protected]
FAIR ISLE: WESTERLY VEERING NORTHERLY 4 OR 5. WINTRY SHOWERS. MAINLY GOOD.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
#2 lore raw
In reply to Dan Kegel

In article <[email protected]>,

Quoted 6 lines · Tony Finch
Quoted 3 lines · Dan Kegel

Tony, are people using the TCP_NOPUSH define as a way to detect the presence of T/TCP support?

No, MSG_EOF is the right way to do that.

However, I think ank is at least partially correct: TCP_NOPUSH has some magic behaviour for sockets in listen state, and turns on at least some T/TCP semantics, if I remember correctly. Tony?

If I remember correctly, may I suggest something: make a new BSD option called (ehh, just random name ;) TCP_CORK, and make the old BSD TCP_NOPUSH option be a superset of TCP_CORK that also turns on T/TCP on listen sockets.

Linux TCP_CORK doesn't have anything to do with T/TCP (not surprisingly, as T/TCP is considered a broken protocol in Linux and other circles).

And Linux TCP_CORK _is_ used on listen sockets: it makes sockets that are accepted from the listen socket have the corking semantics. In contrast, BSD TCP_NOPUSH, I think, has this overloading issue..

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/