This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: TCP_CORK (aka TCP_NOPUSH) does not work
- From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin" <cygwin at cygwin dot com>
- To: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Date: Wed, 31 Jul 2019 04:48:19 +0000
- Subject: Re: TCP_CORK (aka TCP_NOPUSH) does not work
- Arc-authentication-results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=ncbi.nlm.nih.gov;dmarc=pass action=none header.from=ncbi.nlm.nih.gov;dkim=pass header.d=ncbi.nlm.nih.gov;arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7AjHk6Rg1Gvm/h/lgH3Lsx4cNWupzQagQr2YGskcAoo=; b=HGXmjiiEZ+lDAYkVjuhJTm7xFoYaSCS+DgxNJ/GUW9qZwD2JEDcgnAKdEAOGlinWG6G94NQNQzxlbPJNxk6MAEFM8YofPW2cRKZZVqOek5uYMleZosREYNOwPUsja2fHvok9CEy8TJNrxLmyKMG2MlRj+kcUPSuCikHJwOXBwxbLRvuw5oZj6Np+ce4aUgAtev9QmF/0ENfRyh+KMZFldUpxgetJOo6BoeAHzLthM/PFQ8NIhDxsokftkML51pAyDTx1Cg09lN/K7/SnQjOZP5UmbwfnYRE9o5cwT+Jg3OIS70plqjd9A0K7e3x+elpaOkvSQ48nopiGOZD62Viveg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ML54XSWgoOJ7xmwUrfTX4ZsJUHtahGQbM7IUAPmAz5VAOMwpUAx34MBnLTUPWPhckBUqAysmJ9SuZnZ7DO6ly3DSHSjoPW1dQJtfRQL3MUekJbX6n0jx7lTPk/7tm4oKyAyVOscPEY9FvG6Pu+0iMHjCcSddt2cGMDHpd3NhbnZsaQKHbFZjPZOKerfboLk8B2NIW3mOnfzWQd3iYKepdncJMwlBVNs8IfebIK40W6I3s2Rvlu0/boVaCfLZj6Fti6JrPCmm4wOsk1TCPrmB89bIeIBJD+mQSCRYtMN2AfFj17qmdEz9tZy/qqbiyua4yIYKnfCkoG69PESLRnInFA==
- Ironport-sdr: ybZi0R7X6FxhZjtz5hJEfVQV4MxcbX8cak7TC2oAG6aad0C/w2DE296ssG8iwQsLOSilxSSl2t 7fYLtB3c2G3nf7m4063yacTpHdTP6EvgZ8NXes4JfLEzNICN75zqMSDqFoqbkZrjeKFK6y3uZg 6mhM4YzFZuUIqgsDM3a2ZCPZ4CnUT54xnAAqM6GTX461g0dHOGytmG13IMdZG4uTgNf92pVspX upSIkMkrTY4ZO3PkgyWJ+v5Xmm28dPrMZf6vQ/biQ1/YSIswEWavhRaRu5SMWN8NSIEhS6udAw 6Vo=
- Reply-to: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr at ncbi dot nlm dot nih dot gov>
> Regular SO options on Windows:
I did not ask about Windows options. I asked about a feature that is defined in Cygwin yet appears not functional.
> You can abuse Nagle to get similar behaviour cross-platform:
This is not the same thing!
> ENOPROTOOPT (109)... "The option is not supported by the protocol."
Indeed the textual description does not match, and should be changed in Cygwin. Although, I'm sure it was copied over from Linux, which does not define it properly (probably, historically), either:
#define ENOPROTOOPT 92 /* Protocol not available */
BTW, Windows does that correctly:
WSAENOPROTOOPT (10042) = "Bad protocol option"
> If a socket option is defined, perhaps for compatibility, it should either be
> used or ignored, rather than giving an error.
> If you are not going to support a socket option, and generate an error, it would
> be better to not define the option and generate the error at compile time,
> instead of failing at run time.
Who are you suggesting this to?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple