Subject: Re: Why is my rmt so slow or what takes exactly 0.2 seconds?
To: Jonathan Stone <jonathan@Pescadero.dsg.stanford.edu>
From: Bill Studenmund <wrstuden@netbsd.org>
List: tech-net
Date: 08/29/2005 17:41:32
--Er1qpsOqk0l6oMce
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 29, 2005 at 12:17:17PM -0700, Jonathan Stone wrote:
> In message <20050828103356.GA15534@orion.intra.net>,
> Edgar =3D?iso-8859-1?B?RnXf?=3D=20
> writes:
>=20
> >On Thu, Aug 25, 2005 at 11:50:52AM -0700, Bill Studenmund wrote:
>=20
> >What I was hoping all the time is that this 0.2 second interval was trig=
gering
> >someone's memory.
> >
> >If running out of input, how long would the TCP code wait before timing =
out
> >and transmitting a partially filled segment?
>=20
> 0.2 seconds is the "fast" (5Hz) TCP timeout. =20
>=20
> This is probably a stupid question, and I apologize in advance if it
> is, but: are you sure rmt is turning off Nagle with setsockopt()
> TCP_NODELAY?

I don't know about rmt, but I know my test application is.

Take care,

Bill

--Er1qpsOqk0l6oMce
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFDE6s8Wz+3JHUci9cRAja2AJ4qTRF+BPbA3RElhYCO9aCvkrN2yACeJ/rZ
sZNhELUfXnuw1uqPdlzk1fk=
=mNEv
-----END PGP SIGNATURE-----

--Er1qpsOqk0l6oMce--