From: "Haar János" <djani22@netcenter.hu>
To: "Con Kolivas" <kernel@kolivas.org>
Cc: <nickpiggin@yahoo.com.au>, <cw@f00f.org>, <linux-kernel@vger.kernel.org>
Subject: Re: swapper: page allocation failure.
Date: Mon, 22 May 2006 17:08:58 +0200 [thread overview]
Message-ID: <031001c67db1$a8c4a1e0$1800a8c0@dcccs> (raw)
In-Reply-To: <200605222117.27433.kernel@kolivas.org>
----- Original Message -----
From: "Con Kolivas" <kernel@kolivas.org>
To: <linux-kernel@vger.kernel.org>
Cc: "Haar János" <djani22@netcenter.hu>; "Nick Piggin"
<nickpiggin@yahoo.com.au>; <cw@f00f.org>
Sent: Monday, May 22, 2006 1:17 PM
Subject: Re: swapper: page allocation failure.
> On Monday 22 May 2006 17:41, Haar János wrote:
> > ----- Original Message -----
> > From: "Nick Piggin" <nickpiggin@yahoo.com.au>
> > > Yeah, as I said, block device's pagecache (aka buffercache) can't
> > > use highmem. If nbd can export regular files as block devices, or
> > > you use loop devices from regular files, that might help (or slow
> > > things down :P).
> >
> > Hmm.
> > That sounds bad.
> > I think, if highmem is unreachable some times that makes lowmem more
> > valuable!
> > The kernel needs to keep (reserve) it free as much as possible.
> > The buffer-cache is an unimportant thing next to keeping lowmem free,
but
> > it is blocks the performance and wastes the systems resources!
> >
> > It is possible any workaround?
>
> Try with one of the alternative vmsplit options that gives you more
lowmem?
> That might break certain applications though.
total used free shared buffers cached
Mem: 4049724 4021196 28528 0 16384 3217288
Low: 4049724 4021196 28528
High: 0 0 0
-/+ buffers/cache: 787524 3262200
Swap: 0 0 0
This is an 64 bit machine, the "concentrator".
It looks like use all, the 4G ram as "lowmem".
If i replace the cpu on my nodes to 64bit capable ones, i can use all the
memory as buffer-cache? :-)
Cheers,
Janos
>
> --
> -ck
> -
> 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/
next prev parent reply other threads:[~2006-05-22 15:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 8:10 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
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 [this message]
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='031001c67db1$a8c4a1e0$1800a8c0@dcccs' \
--to=djani22@netcenter.hu \
--cc=cw@f00f.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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
all inboxes | Powered by JetHome®