netdev - 200 millisecond timeouts in TCP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTils4KHXwX79cLG6UvVOaDdddMqx-1tyUL3VtLQC@mail.gmail.com>
Date:	Thu, 3 Jun 2010 15:37:24 -0700
From:	Ivan Novick <novickivan@...il.com>
To:	netdev@...r.kernel.org
Subject: 200 millisecond timeouts in TCP

Hello,

Using tcpdump and systemtap I am seeing that sometimes retransmission
of data is sent after waiting 200 milliseconds.  However sometimes
retransmissions happen quicker.

Is there a specifc event that causes these 200 milisec delays to kick
in?  Are those events identifiable in netstat -s output?

Also do you know if the timeout numbers for TCP are configurable parameters?

I am testing on RHEL5 with this kernel: 2.6.18-164.15.1.el5.

Cheers,
Ivan Novick
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html