From: Pekka Enberg <penberg@kernel.org>
To: "Peter Schüller" <scode@spotify.com>
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Mattias de Zalenski <zalenski@spotify.com>,
linux-mm@kvack.org
Subject: Re: Sudden and massive page cache eviction
Date: Wed, 24 Nov 2010 16:20:30 +0200 [thread overview]
Message-ID: <AANLkTimo1BR=mSJ6wPQwrL4FDNv=_TfanPPTT7uWx7hQ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=mgTHPEYFsryDYnxPa78f-Nr+H7i4+0KPZbxh3@mail.gmail.com>
Hi Peter,
2010/11/24 Peter Schüller <scode@spotify.com>:
>>> Do you have any large page (hugetlbfs) or other multi-order (> 1 page)
>>> allocations happening in the kernel?
>
> I forgot to address the second part of this question: How would I best
> inspect whether the kernel is doing that?
You can, for example, record
cat /proc/meminfo | grep Huge
for large page allocations.
> Looking at the kmalloc() sizes from vmstat -m I have the following on
> one of the machines (so very few larger than 4096). But I suspect you
> are asking for something different?
The "pagesperslab" column of /proc/slabinfo tells you how many pages
slab allocates from the page allocator.
Pekka
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-11-24 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikg-sR97tkG=ST9kjZcHe6puYSvMGh-eA3cnH7X@mail.gmail.com>
2010-11-23 0:11 ` Andrew Morton
2010-11-23 8:38 ` Dave Hansen
2010-11-23 9:44 ` Peter Schüller
2010-11-23 16:19 ` Dave Hansen
2010-11-24 14:02 ` Peter Schüller
2010-11-24 14:14 ` Peter Schüller
2010-11-24 14:20 ` Pekka Enberg [this message]
2010-11-24 15:32 ` Peter Schüller
2010-11-24 17:46 ` Pekka Enberg
2010-11-25 1:18 ` Simon Kirby
2010-11-25 15:59 ` Peter Schüller
2010-12-01 6:36 ` Simon Kirby
2010-11-24 17:32 ` Dave Hansen
2010-11-25 15:33 ` Peter Schüller
2010-12-01 9:15 ` Simon Kirby
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='AANLkTimo1BR=mSJ6wPQwrL4FDNv=_TfanPPTT7uWx7hQ@mail.gmail.com' \
--to=penberg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=scode@spotify.com \
--cc=zalenski@spotify.com \
/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