|
On Wed, Jul 22, 2009 at 14:33, Joseph Mack NA3T<jmack@xxxxxxxx> wrote:
> On Wed, 22 Jul 2009, Graeme Fowler wrote:
>
>> it's also possible under a load of many (thousands of?)
>> connections/second that the IPVS connection table could be
>> overflowing.
>
> this won't happen till there are ($your_memory)/128byte
> connections
128 bytes are no longer true, at least since IPv6 support for IPVS was
merged, but other things have changed as well. In my config it's
264 bytes, but millage may vary.
diff --git a/net/netfilter/ipvs/ip_vs_core.c b/net/netfilter/ipvs/ip_vs_core.c
index b021464..f5538f4 100644
--- a/net/netfilter/ipvs/ip_vs_core.c
+++ b/net/netfilter/ipvs/ip_vs_core.c
@@ -1476,6 +1476,8 @@ static int __init ip_vs_init(void)
}
IP_VS_INFO("ipvs loaded.\n");
+ printk(KERN_INFO "IPVS: sizeof(struct ip_vs_conn)=%Zd\n",
+ sizeof(struct ip_vs_conn));
return ret;
cleanup_conn:
Cheers,
-Hannes
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
