Subject: Re: rdist and net.inet.tcp.ack_on_push=1
To: Robert Elz <kre@munnari.OZ.AU>
From: Ignatios Souvatzis <ignatios@theory.cs.uni-bonn.de>
List: tech-net
Date: 07/29/2003 15:06:06
--/aVve/J9H4Wl5yVO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Mon, Jun 16, 2003 at 06:18:55PM +0700, Robert Elz wrote:
>     Date:        Mon, 16 Jun 2003 09:38:04 +0100
>     From:        David Laight <david@l8s.co.uk>
>     Message-ID:  <20030616093804.J3322@snowdrop.l8s.co.uk>
>=20
>   | IIRC about the only thing the push flag mans is 'send this now and
>   | don't wait for any more data because there won't be any'.
>=20
> These days PUSH means essentially nothing.   Its intent was to tell
> the receiving TCP that it should deliver the data to the application
> (or at least make known to the application that data existed that
> could be fetched) rather than simply buffering it for sometime later.

Ah - so it's more or less the inverse of the Chaosnet
ack-delivery-to-application vs. ack-delivery-to-tcp-stack function.

Regards,
	-is

--/aVve/J9H4Wl5yVO
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQEVAgUBPyZw7zCn4om+4LhpAQFBLgf5AS8K/gItyzPLFsMaHgNBzZ2a1yOAho9Y
V+ccOkJUBvGdRc7yuXj6lxcq49S6rSZxdi3hHuAYY5zi8oPob0FiaWz+EfiUPUas
tCdy3PP9og3NOsB+DSzgfHA37+is+oWFFqTR4eD3lAGtXRnmKMuot3vew6Q78M1f
vwCtXlbmfJk2qgjtU4+57f08jK9P3SdtvnA6HOUAtALFR/Dm2ZUMSmqjtHYVNmUc
dUbbvaff45DlWti8jc1zD8UUkWQSoKM1scTJMaN+ylRGi3xTiGXs4giyOHOAftLc
EZt/Dk6XMplJyK95OdigxghfHwdoMxUl7kutiVpK94sWpYMo3XL4GA==
=9fSS
-----END PGP SIGNATURE-----

--/aVve/J9H4Wl5yVO--