[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48D2A392.6010308@goop.org>
Date: Thu, 18 Sep 2008 11:53:06 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Christoph Lameter <cl@...ux-foundation.org>
CC: Chris Snook <csnook@...hat.com>,
Nick Piggin <nickpiggin@...oo.com.au>,
Hugh Dickens <hugh@...itas.com>,
Linux Memory Management List <linux-mm@...ck.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Avi Kivity <avi@...ranet.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Rik van Riel <riel@...hat.com>,
"Martin J. Bligh" <mbligh@...gle.com>
Subject: Re: Populating multiple ptes at fault time
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists