From: David Gibson <david@gibson.dropbear.id.au>
To: Avi Kivity <avi@argo.co.il>
Cc: linux-kernel@vger.kernel.org, linuxppc64-dev@ozlabs.org
Subject: Re: RFC: Hugepage COW
Date: Thu, 7 Jul 2005 19:24:25 +1000 [thread overview]
Message-ID: <20050707092425.GA10044@localhost.localdomain> (raw)
In-Reply-To: <1120718967.2989.7.camel@blast.q>
On Thu, Jul 07, 2005 at 09:49:27AM +0300, Avi Kivity wrote:
> On Thu, 2005-07-07 at 15:55 +1000, David Gibson wrote:
>
> > MAP_PRIVATE|MAP_WRITE mappings of hugetlbfs. Because the pool of
> > hugepages is limited, a write to a MAP_PRIVATE hugepage region may
> > result in a SIGBUS, if a new hugepage cannot be allocated. This patch
>
> in that case you might allocate regular pages for the new copy.
That's not necessarily possible. On some archs - ppc64 for one -
the mmu has to be set up for hugepages on a granularity greater than
the hugepage size. So you can just arbitrarily substitute normal
pages for hugepages.
--
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-07 11:51 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 [this message]
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
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=20050707092425.GA10044@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=avi@argo.co.il \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.