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]
Date:	Thu, 5 Oct 2006 10:45:46 +0200
From:	Eric Dumazet <dada1@...mosbay.com>
To:	Markus Wenke <M.Wenke@....de>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: to many sockets ?

On Thursday 05 October 2006 10:20, Markus Wenke wrote:
> Eric Dumazet schrieb:

> > Could you post here the result of these commands when your system is
> > using more than 100.000 connections (and before the OOM :) )
>
> Hi,
>
> here the results with 130001 connetions
>
> > cat /proc/meminfo
>
> MemTotal:      3108372 kB
> MemFree:       2114404 kB
> Buffers:          5112 kB
> Cached:          97804 kB
> SwapCached:          0 kB
> Active:         140552 kB
> Inactive:        38948 kB
> HighTotal:     2228160 kB
> HighFree:      2048108 kB
> LowTotal:       880212 kB
> LowFree:         66296 kB

See here ? you have 'only' 880212 kB of LOWMEM, and 66 MB free.
all kernel structures (you can see them in /proc/slabinfo) are lying on this 
zone, no matter you add RAM on your machine (more RAM end up in HighMEM zone, 
wich is basically unused on your setup)

Since you have a 64bits CPU, your best move would be to use a 64bits kernel 
(you can keep all user land in 32bits mode)

With a 64bits kernel, kernel land structures would not be constrained in a 
small area, but can use full RAM.

I'm curious you have so many sockets but few entries in route cache... 
basically all connections come from few machines ?

Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ