netdev - Re: [PATCH] IPVS: Allow boot time change of hash size.

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]

Date:	Tue, 05 Jan 2010 05:56:29 +0100
From:	Patrick McHardy <kaber@...sh.net>
To:	Simon Horman <horms@...ge.net.au>
CC:	netdev@...r.kernel.org, lvs-devel@...r.kernel.org,
	"Catalin(ux) M. BOIE" <catab@...edromix.ro>,
	Mark Bergsma <mark@...imedia.org>,
	Joseph Mack NA3T <jmack@...d.net>,
	Graeme Fowler <graeme@...emef.net>,
	David Miller <davem@...emloft.net>
Subject: Re: [PATCH] IPVS: Allow boot time change of hash size.

Simon Horman wrote:
> From: Catalin(ux) M. BOIE <catab@...edromix.ro>
> 
> IPVS: Allow boot time change of hash size.
> 
> I was very frustrated about the fact that I have to recompile the kernel
> to change the hash size. So, I created this patch.
> 
> If IPVS is built-in you can append ip_vs.conn_tab_bits=?? to kernel
> command line, or, if you built IPVS as modules, you can add
> options ip_vs conn_tab_bits=??.
> 
> To keep everything backward compatible, you still can select the size at
> compile time, and that will be used as default.
> 
> [ horms@...ge.net.au: trivial up-port and minor style fixes ]
> Signed-off-by: Catalin(ux) M. BOIE <catab@...edromix.ro>
> Cc: Mark Bergsma <mark@...imedia.org>
> Signed-off-by: Simon Horman <horms@...ge.net.au>
> 
> ---
> 
> Patrick, please consider applying this. I'd like to do something dynamic.
> But this change is an obvious win in the mean time.

Applied to nf-next-2.6.git, thanks.
--
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