From: Dave Hansen <dave.hansen@intel.com>
To: Luigi Semenzato <semenzato@google.com>
Cc: linux-mm@kvack.org
Subject: Re: swap behavior during fast allocation
Date: Mon, 05 Aug 2013 11:24:22 -0700 [thread overview]
Message-ID: <51FFEDD6.7020906@intel.com> (raw)
In-Reply-To: <CAA25o9RO5+gYCTQuouNsJ5COTWdA+wbPUH--B-STSmySjTxBAQ@mail.gmail.com>
On 08/05/2013 11:04 AM, Luigi Semenzato wrote:
> We can reproduce this by running a few processes that mmap large
> chunks of memory, then randomly touch pages to fault them in. We also
> think this happens when a process writes a large amount of data using
> buffered I/O, and the "Buffers" field in /proc/meminfo exceeds 1GB.
> (This is something that can and should be corrected by using
> unbuffered I/O instead, but it's a data point.)
Where are all the buffers coming from? Most I/O to/from filesystems
should be instantiating relatively modest amounts of Buffers. Are you
doing I/O directly to devices for some reason?
--
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:[~2013-08-05 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 18:04 swap behavior during fast allocation Luigi Semenzato
2013-08-05 18:24 ` Dave Hansen [this message]
2013-08-05 18:30 ` Luigi Semenzato
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=51FFEDD6.7020906@intel.com \
--to=dave.hansen@intel.com \
--cc=linux-mm@kvack.org \
--cc=semenzato@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.