public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Chris Wedgwood <cw@f00f.org>
Cc: Haar J?nos <djani22@netcenter.hu>, linux-kernel@vger.kernel.org
Subject: Re: swapper: page allocation failure.
Date: Sun, 21 May 2006 22:01:29 +1000	[thread overview]
Message-ID: <44705699.3080401@yahoo.com.au> (raw)
In-Reply-To: <20060521102642.GB5582@taniwha.stupidest.org>

Chris Wedgwood wrote:
> On Sun, May 21, 2006 at 11:31:12AM +0200, Haar J?nos wrote:
> 
> 
>>[root@st-0001 /]# uname -a
>>Linux st-0001 2.6.17-rc3-git1 #2 SMP Sun May 21 01:12:22 CEST 2006 i686 i686 i386 GNU/Linux
> 
> 
> did earlier kernels work OK?
> 
> 
>>This is a simple disk node.
>>It serves the md0 array, and uses mem for buffering-caching.
> 
> 
> odd, i looks like you've leaked alot of lowmem but i can't think why
> 
> i've got major (induced) brain-fog right now so i'll have to think
> about it tomorrow sorry

The buffers are buffercache rather than the usual pagecache; due to
nbd I guess. Buffercache cannot be satisfied by highmem.

This would be a relatively uncommon setup, which explains why it
isn't working 100%. I don't know of any reason why reclaim speed
should be worse for buffercache, however one notable thing will be
that zone_normal's lowmem reserve that is untouchable by pagecache
will be eaten by buffercache...

Anyway, increasing /proc/sys/vm/min_free_kbytes should help. Janos,
perhaps you could try doubling it and see how you go?

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  parent reply	other threads:[~2006-05-21 12:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21  8:10 swapper: page allocation failure Haar János
2006-05-21  8:16 ` Chris Wedgwood
2006-05-21  8:37   ` Haar János
2006-05-21  8:47     ` Chris Wedgwood
2006-05-21  9:03       ` Haar János
2006-05-21  9:10         ` Chris Wedgwood
2006-05-21  9:31           ` Haar János
2006-05-21 10:24             ` Chris Wedgwood
2006-05-21 10:42               ` Haar János
2006-05-21 10:26             ` Chris Wedgwood
2006-05-21 10:45               ` Haar János
2006-05-21 12:01               ` Nick Piggin [this message]
2006-05-21 13:58                 ` Haar János
2006-05-22  0:09                   ` Nick Piggin
2006-05-22  7:41                     ` Haar János
2006-05-22 11:17                       ` Con Kolivas
2006-05-22 15:08                         ` Haar János
2006-05-22 15:12                           ` Con Kolivas
2006-05-22 21:06                             ` swapper: page allocation failure. - random reboot problem Haar János
2006-05-23  9:17                               ` Nick Piggin
2006-05-23 10:16                                 ` Haar János
2006-05-23 10:24                                   ` Nick Piggin
2006-05-23 10:31                                     ` Haar János
2006-05-23 10:45                                       ` Nick Piggin
2006-05-23 11:01                                         ` Haar János
2006-05-21  9:23       ` swapper: page allocation failure Haar János
2006-05-21 12:03 ` Andrew Morton
2006-05-21 14:01   ` Haar János

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=44705699.3080401@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=cw@f00f.org \
    --cc=djani22@netcenter.hu \
    --cc=linux-kernel@vger.kernel.org \
    /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