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
Date: Thu, 29 May 2003 17:51:35 -0700 [thread overview]
Message-ID: <20030529175135.7b204aaf.akpm@digeo.com> (raw)
In-Reply-To: <20030529.171114.34756018.davem@redhat.com>
"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.
next prev parent reply other threads:[~2003-05-30 0:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 20:16 2.5.70-mm1 Strangeness Bongani Hlope
[not found] ` <20030529135541.7c926896.akpm@digeo.com>
2003-05-30 0:11 ` David S. Miller
2003-05-30 0:51 ` Andrew Morton [this message]
2003-05-30 0:58 ` David S. Miller
2003-05-30 4:12 ` Bongani Hlope
2003-05-30 5:02 ` Manfred Spraul
2003-05-30 19:25 ` Bongani Hlope
2003-05-30 19:58 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030529175135.7b204aaf.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=bonganilinux@mweb.co.za \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox