Date: Thu, 29 May 2003 17:51:35 -0700
From: Andrew Morton <akpm@digeo.com>
To: "David S. Miller" <davem@redhat.com>
Cc: bonganilinux@mweb.co.za, linux-kernel@vger.kernel.org,
       Manfred Spraul <manfred@colorfullife.com>
Subject: Re: 2.5.70-mm1 Strangeness
Message-Id: <20030529175135.7b204aaf.akpm@digeo.com>
In-Reply-To: <20030529.171114.34756018.davem@redhat.com>
References: <20030529221622.542a6df5.bonganilinux@mweb.co.za>
	<20030529135541.7c926896.akpm@digeo.com>
	<20030529.171114.34756018.davem@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

"David S. Miller" <davem@redhat.com> wrote:
>
>    From: Andrew Morton <akpm@digeo.com>
>    Date: Thu, 29 May 2003 13:55:41 -0700
> 
>    The ip_dst_cache seems unreasonably large.  Unless your desktop is a
>    backbone router or something.
> 
> Lots of DST entries can result on any machine actually.  We create one
> per source address, not just per destination address.  So if you talk
> to a lot of sites, or lots of sites talk to you, you'll get a lot of
> DST entries.
> 
> Regardless, 80MB _IS_ excessive.  That's nearly 400,000 entries.
> It definitely indicates there is a leak somewhere.
> 
> Although it say:
> 
> ip_dst_cache       19470  19470   4096    1    1
> 
> Which is 19470 active objects right?

Yes, 19470 entries.  But note that each entry is 4096 bytes.

Something seems to have gone and bumped the object size from 240 bytes up
to 4096.  This is actually what I want CONFIG_DEBUG_PAGEALLOC to do, but I
don't think it does it yet.  

Bongani, if you have CONFIG_DEBUG_PAGEALLOC enabled then please try turning
it off.  And maybe Manfred can throw some light on what slab has done
there.

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