linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>, Mel Gorman <mgorman@suse.de>,
	Rik van Riel <riel@redhat.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Hugh Dickins <hughd@google.com>,
	Sangseok Lee <sangseok.lee@lge.com>,
	Michael Kerrisk-manpages <mtk.manpages@gmail.com>
Subject: Re: [RFC 1/4] mm: Per process reclaim
Date: Wed, 3 Apr 2013 12:12:42 +0200	[thread overview]
Message-ID: <CAHO5Pa1we3FCoBTSHTO23tzCss4Z-AkZzoGxBYkTy7e5aYmcJw@mail.gmail.com> (raw)
In-Reply-To: <CAHO5Pa0srsWS6ukpxUo=EqCOxRmYa7c_7PDg1YPh7gcMGWPpaw@mail.gmail.com>

> However, the interface is a quite blunt instrument. Would there be any
> virtue in extending it so that an address range could be written to

Here, I did mean to say "an *optional* address range.

Thanks,

Michael

--
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:[~2013-04-03 10:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  6:21 [RFC 1/4] mm: Per process reclaim Minchan Kim
2013-03-25  6:21 ` [RFC 2/4] mm: make shrink_page_list with pages from multiple zones Minchan Kim
2013-03-25  6:21 ` [RFC 3/4] mm: Remove shrink_page Minchan Kim
2013-03-25  6:21 ` [RFC 4/4] mm: Enhance per process reclaim Minchan Kim
2013-04-02 13:25   ` Michael Kerrisk
2013-04-03  0:23     ` Minchan Kim
2013-04-03  6:16       ` Michael Kerrisk (man-pages)
2013-04-03  6:47         ` Michael Kerrisk (man-pages)
2013-04-03  9:17 ` [RFC 1/4] mm: Per " Michael Kerrisk
2013-04-03 23:31   ` Minchan Kim
2013-04-03 10:10 ` Michael Kerrisk
2013-04-03 10:12   ` Michael Kerrisk [this message]
2013-04-03 23:46   ` Minchan Kim

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=CAHO5Pa1we3FCoBTSHTO23tzCss4Z-AkZzoGxBYkTy7e5aYmcJw@mail.gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=minchan@kernel.org \
    --cc=riel@redhat.com \
    --cc=sangseok.lee@lge.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).