netdev - Re: [PATCH] Make CUBIC Hystart more robust to RTT variations

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Mar 2011 09:54:33 +0100
From:	Lucas Nussbaum <lucas.nussbaum@...ia.fr>
To:	Bill Fink <billfink@...dspring.com>
Cc:	Stephen Hemminger <stephen.hemminger@...tta.com>,
	Injong Rhee <rhee@...u.edu>,
	David Miller <davem@...emloft.net>,
	xiyou wangcong <xiyou.wangcong@...il.com>,
	netdev@...r.kernel.org, sangtae ha <sangtae.ha@...il.com>
Subject: Re: [PATCH] Make CUBIC Hystart more robust to RTT variations

On 10/03/11 at 02:17 -0500, Bill Fink wrote:
> On Wed, 9 Mar 2011, Stephen Hemminger wrote:
> 
> > Bill what is the HZ in your kernel config.
> > I am concerned hystart doesn't work well with HZ=100
> 
> HZ=1000
> 
> But I did have tcp_timestamps disabled.  Should I re-run
> the tests with tcp_timestamps enabled?

I ran my tests with timestamps enabled and HZ=250. If you have the
opportunity to run tests in the same config, it would be great. The
HZ=250 vs HZ=1000 difference could explain why it's working.

However, enabling or disabling timestamps shouldn't make a difference,
since the hystart code doesn't use TCP_CONG_RTT_STAMP.
-- 
| Lucas Nussbaum             MCF Université Nancy 2 |
| lucas.nussbaum@...ia.fr         LORIA / AlGorille |
| http://www.loria.fr/~lnussbau/  +33 3 54 95 86 19 |
--
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