linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	marc.smith@esmail.mcc.edu
Subject: Re: VM/VFS bug with large amount of memory and file systems?
Date: Mon, 17 Sep 2007 16:32:57 +0200	[thread overview]
Message-ID: <20070917163257.331c7605@twins> (raw)
In-Reply-To: <13126578-A4F8-43EA-9B0D-A3BCBFB41FEC@cam.ac.uk>

On Mon, 17 Sep 2007 15:04:05 +0100 Anton Altaparmakov <aia21@cam.ac.uk>
wrote:

> They files  
> are attached this time rather than inlined so people don't complain  
> about line wrapping!  (No doubt people will not complain about them  
> being attached!  )-:)

I switched mailer after I learnt about flowed stuffs. Still,
appreciated.

> If I read it correctly it appears all of low memory is eaten up by  
> buffer_heads.
> 
> <quote>
> # name            <active_objs> <num_objs> <objsize> <objperslab>  
> <pagesperslab>
> : tunables <limit> <batchcount> <sharedfactor> : slabdata  
> <active_slabs> <num_s
> labs> <sharedavail>
> buffer_head       12569528 12569535     56   67    1 : tunables   
> 120   60    8 :
> slabdata 187605 187605      0
> </quote>
> 
> That is 671MiB of low memory in buffer_heads.
> 
> But why is the kernel not reclaiming them by getting rid of the page  
> cache pages they are attached to or even leaving the pages around but  
> killing their buffers?

Well, you see, you have this very odd configuration where:

11GB highmem
 1GB normal

pagecache pages go into highmem
buggerheads go into normal

I'm guessing there is no pressure at all on zone_highmem so the
kernel will not try to reclaim pagecache. And because the pagecache
pages are happily sitting there, the buggerheads are pinned and do not
get reclaimed.

--
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>

  parent reply	other threads:[~2007-09-17 14:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15  7:27 Anton Altaparmakov
2007-09-15 10:08 ` Peter Zijlstra
2007-09-15 10:50   ` Anton Altaparmakov
2007-09-15 11:19     ` Peter Zijlstra
2007-09-16  7:22       ` Kyle Moffett
2007-09-16 16:16         ` Peter Zijlstra
2007-09-15 10:52   ` Andrew Morton
2007-09-17 14:04     ` Anton Altaparmakov
2007-09-17 14:09       ` Anton Altaparmakov
2007-09-16 22:28         ` Nick Piggin
2007-09-17 17:04           ` Rik van Riel
2007-09-17 17:12             ` Nick Piggin
2007-09-18 14:41               ` Rik van Riel
2007-09-17 14:32       ` Peter Zijlstra [this message]
2007-09-17 17:11         ` Rik van Riel
2007-09-17 20:15           ` Andrew Morton
2007-09-17 20:46             ` Rik van Riel
2007-09-17 21:11               ` Andrew Morton
2007-09-19 22:12                 ` Rik van Riel
2007-09-19 22:45                   ` Andrew Morton
2007-09-19 22:50                     ` Rik van Riel
2007-09-19 23:29                     ` Christoph Lameter
2007-09-19 23:37                       ` Andrew Morton
2007-10-03 10:51 ` Pavel Machek

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=20070917163257.331c7605@twins \
    --to=peterz@infradead.org \
    --cc=aia21@cam.ac.uk \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marc.smith@esmail.mcc.edu \
    /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