Hi Cilliè, On Thu, 2003-07-03 at 17:04, Cilliè Burger wrote: > Here are the details you requested. > > cat /proc/meminfo > total: used: free: shared: buffers: cached: > Mem: 63598592 62529536 1069056 0 23306240 19935232 > Swap: 200237056 3911680 196325376 > MemTotal: 62108 kB > MemFree: 1044 kB > MemShared: 0 kB > Buffers: 22760 kB > Cached: 19192 kB > SwapCached: 276 kB > Active: 26476 kB > Inact_dirty: 14428 kB > Inact_clean: 2428 kB > Inact_target: 8664 kB > HighTotal: 0 kB > HighFree: 0 kB > LowTotal: 62108 kB > LowFree: 1044 kB > SwapTotal: 195544 kB > SwapFree: 191724 kB > Committed_AS: 6052 kB > > ------------------------------------------------------------ > > > cat /proc/slabinfo > slabinfo - version: 1.1 > kmem_cache 61 70 112 2 2 1 > ip_conntrack 1193 1628 352 127 148 1 ... > inode_cache 17328 19976 496 2497 2497 1 > dentry_cache 17522 23275 112 665 665 1 ... > buffer_head 9797 12040 96 272 301 1 ... > > wc -l /proc/net/ip_conntrack > 1107 /proc/net/ip_conntrack > See, ip_conntrack is only using 1193 * 352 bytes per connection, and the number of connections tracked is quite reasonable. You can also see that a fair amount of RAM is simply used for caching of filesytem operations (see cached: entry of meminfo output and the inode_cache and dentry_cache in slabinfo output). So I wouldn't worry about any memory leaks in netfilter connection tracking. The numbers you provided look quite normal. Regards, Filip
