netdev - Re: [PATCH] ipvs: Make the synchronization interval controllable

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

Message-ID: <Pine.LNX.4.64.0802081656130.10726@bizon.gios.gov.pl>
Date:	Fri, 8 Feb 2008 16:57:47 +0100 (CET)
From:	Krzysztof Oledzki <olel@....pl>
To:	Andi Kleen <andi@...stfloor.org>
cc:	Sven Wegener <sven.wegener@...aler.net>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ipvs: Make the synchronization interval controllable



On Fri, 8 Feb 2008, Andi Kleen wrote:

> Sven Wegener <sven.wegener@...aler.net> writes:
>
>> The default synchronization interval of 1000 milliseconds is too high for a
>> heavily loaded director. Collecting the connection information from one second
>> and then sending it out in a burst will overflow the socket buffer and lead to
>> synchronization information being dropped. Make the interval controllable by a
>> sysctl variable so that users can tune it.
>
> It would be better if the defaults just worked under all circumstances.
> So why not just lower the default?
>
> Or the code could detect overflowing socket buffers and lower the
> value dynamically.

We can also start sending when amount of data reaches defined level.

Best regards,

 				Krzysztof Olędzki