netdev - Re: Increasing TCP initial cwnd

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]

Date:	Mon, 26 Oct 2009 17:07:45 +0200
From:	Yair Gottdenker <yairgott@...il.com>
To:	Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>,
	netdev@...r.kernel.org
Subject: Re: Increasing TCP initial cwnd

Thanks,

I already had a look in it. Their changes that are related to changing
the initial cwnd  (snd_cwnd) are in several places in the patch:
1. tcp_ipv4.c in function tcp_init_cwnd. since currently I am working
with no metric this is irrelevant.
2. tcp_ipv4.c: in function tcp_v4_init_sock, which I applied
3. tcp_minisocks.c - which I applied
. They patched kernel 2.6.18.8 which is very old and there were a lot
of changes since that in the kernel tcp layer. I didn't test their
patch but applying the same logic to 2.6.31.3 doesn't seems to change
initial window size.

It is clear that in order to correctly make the change to the initial
cwnd, one should apply changes to many more scenarios like setting the
initial cwnd after idle time and more. I want to proceed step by step,
first the naive changes to make it work.

On Mon, Oct 26, 2009 at 4:38 PM, Ilpo Järvinen
<ilpo.jarvinen@...sinki.fi> wrote:
> On Mon, 26 Oct 2009, Yair Gottdenker wrote:
>
>> Thanks for the response.
>> I disabled metric by: net.ipv4.tcp_no_metrics_save = 1 in sysctl.conf.
>> But just after the call to tcp_init_metrics in tcp_input.c there is
>> also a call to: tcp_init_congestion_control which calls the congestion
>> control algorithm that is in used. I created my own and in the init
>> function I set the snd_cwnd to 10 and still there is no change and
>> only 4 segments are initially sent.
>> You are right tcp_slow_start has nothing to do with the cwnd size, I
>> mistakenly thought that the initial flow enters that function.
>
> Hopefully you don't mess up anything in there.
>
> Please see from http://www.cs.helsinki.fi/research/iwtcp/kernel-patch/
> I haven't had time/interest to bring it up to date but at least there's
> very clearly shown how the initial window can be configured through a
> sysctl (though don't try to patch it to late kernels, it would just be
> a never ending pain for you :-)).
>
>> What do you mean RW? do you mean tcp read/write buffer size?
>
> RW = Restart Window (RFC2681 IIRC, nowadays also in RFC 5681 I think).
> ...It is related to slow-start after idle.
>
> --
>  i.
>
--
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