netdev - Re: [PATCH 2/2][TCP] YeAH-TCP: limited slow start exported function

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]

Message-Id: <20070222.002704.34758758.davem@davemloft.net>
Date:	Thu, 22 Feb 2007 00:27:04 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	jheffner@....edu
Cc:	angelo.castellani@...il.com, netdev@...r.kernel.org,
	andrea.baiocchi@...roma1.it, francesco@....infocom.uniroma1.it
Subject: Re: [PATCH 2/2][TCP] YeAH-TCP: limited slow start exported function

From: John Heffner <jheffner@....edu>
Date: Mon, 19 Feb 2007 16:00:06 -0500

> I'd prefer to make it apply automatically across all congestion controls 
> that do slow-start, and also make the max_ssthresh parameter 
> controllable via sysctl.  This patch (attached) should implement this. 
> Note the default value for sysctl_tcp_max_ssthresh = 0, which disables 
> limited slow-start.  This should make ABC apply during LSS as well.
> 
> Note the patch is compile-tested only!  I can do some real testing if 
> you'd like to apply this Dave.

I'll apply this, but could you please also when making suggestions
like this provide the patch necessary to kill the function added for
YeaH and the call site in the YeaH algorithm?

When people post conflicting code bits for this for inclusion, it
makes work very difficult for me.

What I want to do right now is back everything out and let you guys
sort it out, but I don't want to do that because it would mean that
I just wasted an entire hour reviewing the YeaH patches. :-/

-
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