mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <christoph@lameter.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linux-kernel@vger.kernel.org, linuxppc64-dev@ozlabs.org
Subject: Re: RFC: Hugepage COW
Date: Thu, 14 Jul 2005 10:24:33 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.62.0507141022440.14347@graphe.net> (raw)
In-Reply-To: <20050707055554.GC11246@localhost.localdomain>

On Thu, 7 Jul 2005, David Gibson wrote:

> Now that the hugepage code has been consolidated across the
> architectures, it becomes much easier to implement copy-on-write.
> Hugepage COW is of limited utility of itself, however, it is
> essentially a prerequisite for any of a number of methods of allowing
> userland programs to automatically use hugepages without code changes
> e.g. hugepage malloc() libraries, implicit hugepage mmap(), hugepage
> ELF segments.  For certain applications (particularly enormous HPC
> FORTRAN programs), these can result in a large performance
> improvement.
> 
> Thoughts?  Flames?

Great stuff. I am glad that you are cleaning up the hugepages and are 
making progress improving them. What are your thoughts on implementing 
fault handling for huge pages?



  parent reply	other threads:[~2005-07-14 17:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07  5:55 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 [this message]
2005-07-15  1:14   ` David Gibson
2005-07-15  2:00     ` Christoph Lameter
2005-07-15  4:21       ` David Gibson
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=Pine.LNX.4.62.0507141022440.14347@graphe.net \
    --to=christoph@lameter.com \
    --cc=david@gibson.dropbear.id.au \
    --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

all inboxes | Powered by JetHome®