From: David Gibson <david@gibson.dropbear.id.au>
To: Christoph Lameter <christoph@lameter.com>
Cc: linux-kernel@vger.kernel.org, linuxppc64-dev@ozlabs.org
Subject: Re: RFC: Hugepage COW
Date: Fri, 15 Jul 2005 14:21:46 +1000 [thread overview]
Message-ID: <20050715042146.GE7750@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.62.0507141858220.21873@graphe.net>
On Thu, Jul 14, 2005 at 07:00:11PM -0700, Christoph Lameter wrote:
> On Fri, 15 Jul 2005, David Gibson wrote:
>
> > Well, the COW patch implements a fault handler, obviously. What
> > specifically where you thinking about?
>
> About a fault handler of course and about surrounding scalability issues.
> I worked on some hugepage related patches last fall. Have you had a look
> at the work of Ken, Ray and me on the subject?
I'm still not at all sure what you're getting at. Do you mean the
demand-allocation patches which were floating around at some point - I
gather they're important for doing sensible NUMA allocation of
hugepages. They have a small overlap with the COW code, in the fault
handler, but not much.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/people/dgibson
next prev parent reply other threads:[~2005-07-15 5:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 5:55 RFC: Hugepage COW David Gibson
2005-07-07 6:49 ` Avi Kivity
2005-07-07 9:24 ` David Gibson
2005-07-07 12:53 ` Stephen Rothwell
2005-07-08 2:44 ` David Gibson
2005-07-14 17:24 ` Christoph Lameter
2005-07-15 1:14 ` David Gibson
2005-07-15 2:00 ` Christoph Lameter
2005-07-15 4:21 ` David Gibson [this message]
2005-07-15 4:34 ` Christoph Lameter
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=20050715042146.GE7750@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=christoph@lameter.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
/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