From: Tony Finch <dot@dotat.at>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dank@alumni.caltech.edu, Linus Torvalds <torvalds@transmeta.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tony Finch <dot@dotat.at>
Subject: Re: TCP_NOPUSH on FreeBSD, TCP_CORK on Linux (was: Is sendfile all that
Date: Mon, 5 Feb 2001 23:49:25 +0000 [thread overview]
Message-ID: <20010205234925.J70673@hand.dotat.at> (raw)
In-Reply-To: <3A7F3420.A3B10510@alumni.caltech.edu> <E14Puvx-0004TB-00@the-village.bc.nu>
In-Reply-To: <E14Puvx-0004TB-00@the-village.bc.nu>
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> How close is TCP_NOPUSH to behaving identically to TCP_CORK now?
>> If it does behave identically, it might be time to standardize
>> the symbolic name for this option, to make apps more portable
>> between the two OS's. (It'd be nice to also standardize the
>> numeric value, in the interest of making the ABI's more compatible, too.)
>
>That one isnt practical because of the way the implementations handle
>boolean options. BSD uses bitmask based option setting for the basic
>options and Linus uses switch statements
No, that's only true for some of the socket-level options. For the TCP
options there isn't a direct correspondance between the option number
and the number of the flag in the PCB.
Tony.
--
f.a.n.finch fanf@covalent.net dot@dotat.at
"Dead! And yet there he stands!"
-
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 prev parent reply other threads:[~2001-02-05 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A66729E.3E9E3C64@alumni.caltech.edu>
[not found] ` <Pine.LNX.4.10.10101172046170.17109-100000@penguin.transmeta.com>
[not found] ` <20010202013104.A48377@hand.dotat.at>
[not found] ` <20010205225411.E70673@hand.dotat.at>
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 [this message]
2001-02-06 18:41 ` kuznet
2001-02-05 23:24 ` TCP_NOPUSH on FreeBSD, TCP_CORK on Linux (was: Is sendfile all that sexy?) Tony Finch
2001-02-08 1:27 TCP_NOPUSH on FreeBSD, TCP_CORK on Linux (was: Is sendfile all that Dan Kegel
2001-02-08 3:58 ` Tony Finch
2001-02-08 19:52 ` Linus Torvalds
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=20010205234925.J70673@hand.dotat.at \
--to=dot@dotat.at \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dank@alumni.caltech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox