linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Matthew Wilcox <matthew.r.wilcox@intel.com>,
	lsf-pc@lists.linux-foundation.org, "Reddy,
	Dheeraj" <dheeraj.reddy@intel.com>
Cc: "Kleen, Andi" <andi.kleen@intel.com>,
	"Chen, Tim C" <tim.c.chen@intel.com>,
	Linux-MM <linux-mm@kvack.org>
Subject: [LSF/MM TOPIC] Reclaim in the face of really fast I/O
Date: Thu, 15 Jan 2015 13:00:07 -0800	[thread overview]
Message-ID: <54B82A57.9060000@intel.com> (raw)

I/O devices are only getting faster.  In fact, they're getting closer
and closer to memory in latency and bandwidth.  But the VM is still
designed to do very orderly and costly procedures to reclaim memory, and
the existing algorithms don't parallelize particularly well.  They hit
contention on mmap_sem or the lru locks well before all of the CPU
horsepower that we have can be brought to bear on reclaim.

Once the latency to bring pages in and out of storage becomes low
enough, reclaiming the _right_ pages becomes much less important than
doing something useful with the CPU horsepower that we have.

We need to talk about ways to do reclaim with lower CPU overhead and to
parallelize more effectively.

There has been some research in this area by some folks at Intel and we
could quickly summarize what has been learned so far to help kick off a
discussion.

--
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>

             reply	other threads:[~2015-01-15 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 21:00 Dave Hansen [this message]
2015-01-16  1:21 ` [Lsf-pc] [LSF/MM TOPIC] Reclaim in the face of really fast I/O Sasha Levin
2015-01-16  1:32   ` Sasha Levin

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=54B82A57.9060000@intel.com \
    --to=dave.hansen@intel.com \
    --cc=andi.kleen@intel.com \
    --cc=dheeraj.reddy@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=matthew.r.wilcox@intel.com \
    --cc=tim.c.chen@intel.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;
as well as URLs for NNTP newsgroup(s).