From: Dan Kegel <dank@alumni.caltech.edu>
To: kuznet@ms2.inr.ac.ru,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dot@dotat.at
Subject: Re: TCP_NOPUSH on FreeBSD, TCP_CORK on Linux (was: Is sendfile all that
Date: Wed, 07 Feb 2001 17:27:40 -0800 [thread overview]
Message-ID: <3A81F60C.7C1DB09A@alumni.caltech.edu> (raw)
Alexy wrote:
> > > 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/
next reply other threads:[~2001-02-08 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 1:27 Dan Kegel [this message]
2001-02-08 3:58 ` TCP_NOPUSH on FreeBSD, TCP_CORK on Linux (was: Is sendfile all that Tony Finch
2001-02-08 19:52 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2001-02-05 23:15 TCP_NOPUSH on FreeBSD, TCP_CORK on Linux (was: Is sendfile all that sexy?) Dan Kegel
2001-02-05 23:20 ` TCP_NOPUSH on FreeBSD, TCP_CORK on Linux (was: Is sendfile all that Alan Cox
2001-02-05 23:24 ` Dan Kegel
2001-02-05 23:49 ` Tony Finch
2001-02-06 18:41 ` kuznet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A81F60C.7C1DB09A@alumni.caltech.edu \
--to=dank@alumni.caltech.edu \
--cc=dot@dotat.at \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.