From: Richard Kennedy <richard@rsk.demon.co.uk>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Christoph Lameter <cl@linux-foundation.org>,
penberg@cs.helsinki.fi, mpm@selenic.com,
linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] slub: increasing order reduces memory usage of some key caches
Date: Thu, 17 Jul 2008 10:48:33 +0100 [thread overview]
Message-ID: <1216288113.3061.2.camel@castor.localdomain> (raw)
In-Reply-To: <20080716195237.GA9127@csn.ul.ie>
On Wed, 2008-07-16 at 20:52 +0100, Mel Gorman wrote:
> On (16/07/08 08:21), Christoph Lameter didst pronounce:
> > Richard Kennedy wrote:
> >
> >
> > > on my amd64 3 gb ram desktop typical numbers :-
> > >
> > > [kernel,objects,pages/slab,slabs,total pages,diff]
> > > radix_tree_node
> > > 2.6.26 33922,2,2423 4846
> > > +patch 33541,4,1165 4660,-186
> > > dentry
> > > 2.6.26 82136,1,4323 4323
> > > +patch 79482,2,2038 4076,-247
> > > the extra dentries would use 136 pages but that still leaves a saving of
> > > 111 pages.
> >
> > Good numbers....
> >
>
> Indeed. clearly internal fragmentation is a problem.
>
> > > Can anyone suggest any other tests that would be useful to run?
> > > & Is there any way to measure what impact this is having on
> > > fragmentation?
> >
> > Mel would be able to tell you that but I think we better figure out what went wrong first.
> >
>
> For internal fragmentation, there is this crappy script:
> http://www.csn.ul.ie/~mel/intfrag_stat
>
> run it as intfrag_stat -a and it should tell you what precentage of
> memory is being wasted for dentries. The patch should show a difference
> for the dentries.
>
> How it would affect external fragmentation is harder to guess. It will
> put more pressure for high-order allocations but at a glance, dentries
> are using GFP_KERNEL so it should not be a major problem.
> /proc/pagetypeinfo is the file to watch. If the count for "reclaimable"
> arenas is higher and climbing over time, it will indiate that external
> fragmentation would eventually become a problem.
>
Mel,
Thanks for the info & the script. I'll give it a try & see what we get.
Richard
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-07-17 9:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 12:29 Richard Kennedy
2008-07-16 13:21 ` Christoph Lameter
2008-07-16 13:58 ` Richard Kennedy
2008-07-16 14:03 ` Christoph Lameter
2008-07-16 14:30 ` Richard Kennedy
2008-07-16 14:33 ` Vegard Nossum
2008-07-16 14:46 ` Christoph Lameter
2008-07-18 9:57 ` Richard Kennedy
2008-07-18 14:17 ` Christoph Lameter
2008-07-18 14:20 ` Christoph Lameter
2008-07-18 14:42 ` Richard Kennedy
2008-07-18 14:55 ` Christoph Lameter
2008-07-18 15:22 ` Richard Kennedy
2008-07-18 17:13 ` Christoph Lameter
2008-07-16 19:52 ` Mel Gorman
2008-07-17 9:48 ` Richard Kennedy [this message]
2008-07-16 15:52 ` Christoph Lameter
2008-07-16 15:59 ` Christoph Lameter
2008-07-17 10:09 ` Richard Kennedy
2008-07-17 16:56 ` Christoph Lameter
2008-07-18 10:17 ` Richard Kennedy
2008-07-18 14:21 ` Christoph Lameter
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=1216288113.3061.2.camel@castor.localdomain \
--to=richard@rsk.demon.co.uk \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
/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