From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Pavel Machek <pavel@ucw.cz>,
Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: swapping when there's a free memory
Date: Tue, 27 Apr 2010 10:35:17 +0900 [thread overview]
Message-ID: <20100427103517.ae0658cf.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20100426153333.93c03e98.akpm@linux-foundation.org>
On Mon, 26 Apr 2010 15:33:33 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Sun, 25 Apr 2010 09:13:49 +0200
> Pavel Machek <pavel@ucw.cz> wrote:
>
> > Hi!
> >
> > > I captured this output of vmstat. The machine was freeing cache and
> > > swapping out pages even when there was a plenty of free memory.
> > >
> > > The machine is sparc64 with 1GB RAM with 2.6.34-rc4. This abnormal
> > > swapping happened during running spadfsck --- a fsck program for a custom
> > > filesystem that caches most reads in its internal cache --- so it reads
> > > buffers and allocates memory at the same time.
> > >
> > > Note that sparc64 doesn't have any low/high memory zones, so it couldn't
> > > be explained by filling one zone and needing to allocate pages in it.
> >
> > Fragmented memory + high-order allocation?
>
> Yeah, could be. I wonder which slab/slub/slob implementation you're
> using, and what page sizes it uses for dentries, inodes, etc. Can you
> have a poke in /prob/slabinfo?
>
And please /proc/buddyinfo and /proc/zoneinfo when the system is swappy.
Thanks,
-Kame
>
> > > This abnormal behavior doesn't happen everytime, it happend about twice
> > > for many spadfsck attempts.
> >
> > ...yep, that would be random.
>
> --
> 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/
>
--
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:[~2010-04-27 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.1.10.1004220248280.19246@artax.karlin.mff.cuni.cz>
2010-04-26 22:31 ` Andrew Morton
[not found] ` <20100425071349.GA1275@ucw.cz>
2010-04-26 22:33 ` Andrew Morton
2010-04-27 1:35 ` KAMEZAWA Hiroyuki [this message]
2010-04-30 3:52 ` Mikulas Patocka
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=20100427103517.ae0658cf.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=pavel@ucw.cz \
/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