linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux.com>
To: Dave Chinner <david@fromorbit.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	linux-mm@kvack.org, akpm@linux-foundation.org, npiggin@kernel.dk,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	kamezawa.hiroyu@jp.fujitsu.com, Mel Gorman <mel@csn.ul.ie>,
	Minchan Kim <minchan.kim@gmail.com>
Subject: Re: [PATCH 0/3] Unmapped page cache control (v5)
Date: Sun, 3 Apr 2011 13:41:20 -0500 (CDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1104031339120.15317@router.home> (raw)
In-Reply-To: <20110402011040.GG6957@dastard>

On Sat, 2 Apr 2011, Dave Chinner wrote:

> Fundamentally, if you just switch off memory reclaim to avoid the
> latencies involved with direct memory reclaim, then all you'll get
> instead is ENOMEM because there's no memory available and none will be
> reclaimed. That's even more fatal for the system than doing reclaim.

Not for my use cases here. No one will die if reclaim happens but its bad
for the bottom line. Reducing the chance of memory reclaim occurring in a
critical section is sufficient.

--
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 internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2011-04-03 18:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30  5:30 Balbir Singh
2011-03-30  5:31 ` [PATCH 1/3] Move zone_reclaim() outside of CONFIG_NUMA (v5) Balbir Singh
2011-03-30  5:31 ` [PATCH 2/3] Refactor zone_reclaim code (v5) Balbir Singh
2011-03-30  5:32 ` [PATCH 3/3] Provide control over unmapped pages (v5) Balbir Singh
2011-03-30 23:35   ` Andrew Morton
2011-03-31  5:52     ` Balbir Singh
2011-03-30 23:36 ` [PATCH 0/3] Unmapped page cache control (v5) Andrew Morton
2011-03-31  5:27   ` Balbir Singh
2011-03-31  5:32     ` Andrew Morton
2011-04-01 17:31       ` Balbir Singh
2011-03-31  5:40 ` KOSAKI Motohiro
2011-03-31  8:28   ` Balbir Singh
2011-04-01  7:56     ` KOSAKI Motohiro
2011-04-01 13:12       ` Balbir Singh
2011-04-01 13:21         ` KOSAKI Motohiro
2011-04-01 18:04           ` Balbir Singh
2011-04-03  9:39             ` KOSAKI Motohiro
2011-03-31 20:13   ` Christoph Lameter
2011-04-01 13:17     ` KOSAKI Motohiro
2011-04-01 14:50       ` Christoph Lameter
2011-04-03  9:44         ` KOSAKI Motohiro
2011-04-03 18:45           ` Christoph Lameter
2011-04-01 23:10       ` Satoru Moriya
2011-04-02  1:10       ` Dave Chinner
2011-04-03  9:32         ` KOSAKI Motohiro
2011-04-04  0:19           ` Dave Chinner
2011-04-04 12:05             ` KOSAKI Motohiro
2011-04-03 18:41         ` Christoph Lameter [this message]
2011-03-31 21:40 ` Dave Chinner
2011-04-01  3:08   ` Balbir Singh
2011-04-01  5:31     ` Dave Chinner
2011-04-01  3:18   ` KOSAKI Motohiro

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=alpine.DEB.2.00.1104031339120.15317@router.home \
    --to=cl@linux.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=david@fromorbit.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=minchan.kim@gmail.com \
    --cc=npiggin@kernel.dk \
    /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