linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Chris Snook <csnook@redhat.com>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	Hugh Dickens <hugh@veritas.com>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Avi Kivity <avi@qumranet.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Rik van Riel <riel@redhat.com>,
	"Martin J. Bligh" <mbligh@google.com>
Subject: Re: Populating multiple ptes at fault time
Date: Thu, 18 Sep 2008 11:53:06 -0700	[thread overview]
Message-ID: <48D2A392.6010308@goop.org> (raw)
In-Reply-To: <48D29AFB.5070409@linux-foundation.org>

Christoph Lameter wrote:
> I had a patch like that a couple of years back but it was not accepted.
>
> http://www.kernel.org/pub/linux/kernel/people/christoph/prefault/
>
> http://readlist.com/lists/vger.kernel.org/linux-kernel/14/70942.html
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0503.1/1292.html
>
>   

Thanks, that was exactly what I was hoping to see.  I didn't see any
definitive statements against the patch set, other than a concern that
it could make things worse.  Was the upshot that no consensus was
reached about how to detect when its beneficial to preallocate anonymous
pages?

Martin, in that thread you mentioned that you had tried pre-populating
file-backed mappings as well, but "Mmmm ... we tried doing this before
for filebacked pages by sniffing the
pagecache, but it crippled forky workloads (like kernel compile) with the
extra cost in zap_pte_range, etc. ".

Could you describe, or have a pointer to, what you tried and how it
turned out?  Did you end up populating so many (unused) ptes that
zap_pte_range needed to do lots more work?

Christoph (and others): do you think vm changes in the last 4 years
would have changed the outcome of these results?


Thanks,
    J

--
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:[~2008-09-18 18:53 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 17:47 Jeremy Fitzhardinge
2008-09-17 18:28 ` Rik van Riel
2008-09-17 21:47   ` Jeremy Fitzhardinge
2008-09-17 20:02 ` Chris Snook
2008-09-17 21:45   ` Jeremy Fitzhardinge
2008-09-18 18:16     ` Christoph Lameter
2008-09-18 18:53       ` Jeremy Fitzhardinge [this message]
2008-09-18 19:39         ` Christoph Lameter
2008-09-18 22:21           ` KOSAKI Motohiro
2008-09-18 20:52         ` Martin Bligh
2008-09-18 20:53           ` Chris Snook
2008-09-18 21:11             ` Martin Bligh
2008-09-18 21:13               ` Christoph Lameter
2008-09-18 21:21                 ` Martin Bligh
2008-09-18 21:32                   ` Christoph Lameter
2008-09-18 21:49                     ` MinChan Kim
2008-09-18 21:58                       ` Christoph Lameter
2008-09-18 22:08                         ` Martin Bligh
2008-09-18 22:11                           ` Christoph Lameter
2008-09-18 22:18                             ` Martin Bligh
2008-09-18 22:22                               ` Jeremy Fitzhardinge
2008-09-18 22:23                             ` Chris Snook
2008-09-18 23:16                               ` MinChan Kim
2008-09-17 22:02 ` Avi Kivity
2008-09-17 22:30   ` Jeremy Fitzhardinge
2008-09-17 22:47     ` Avi Kivity
2008-09-17 23:02       ` Jeremy Fitzhardinge
2008-09-18 20:26         ` Avi Kivity
2008-09-18 22:18           ` Jeremy Fitzhardinge
2008-09-18 23:38             ` Avi Kivity
2008-09-19  0:00               ` Jeremy Fitzhardinge
2008-09-19  0:20                 ` Avi Kivity
2008-09-19  0:42                   ` Jeremy Fitzhardinge
2008-09-24 12:31                     ` Avi Kivity
2008-09-25 18:32                       ` Jeremy Fitzhardinge
2008-09-26 10:26                         ` Martin Schwidefsky
2008-09-19 17:45   ` Benjamin Herrenschmidt
2008-09-17 23:50 ` MinChan Kim
2008-09-18  6:58   ` KOSAKI Motohiro
2008-09-18  7:26   ` KAMEZAWA Hiroyuki

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=48D2A392.6010308@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@linux-foundation.org \
    --cc=avi@qumranet.com \
    --cc=cl@linux-foundation.org \
    --cc=csnook@redhat.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@google.com \
    --cc=nickpiggin@yahoo.com.au \
    --cc=riel@redhat.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