public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
	William Lee Irwin III <wli@holomorphy.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Hugepages demand paging V2 [0/8]: Discussion and overview
Date: Wed, 27 Oct 2004 15:23:17 +1000	[thread overview]
Message-ID: <20041027052317.GG1676@zax> (raw)
In-Reply-To: <Pine.LNX.4.58.0410251825020.12962@schroedinger.engr.sgi.com>

On Mon, Oct 25, 2004 at 06:26:42PM -0700, Christoph Lameter wrote:
> Changes from V1:
> - support huge pages in flush_dcache_page on various architectures
> - revised simple numa allocation
> - do not include update_mmu_cache in set_huge_pte. Require huge_update_mmu_cache
> 
> This is a revised edition of the hugetlb demand page patches by
> Kenneth Chen which were discussed in the following thread in August 2004
> 
> http://marc.theaimsgroup.com/?t=109171285000004&r=1&w=2
> 
> The initial post by Ken was in April in
> 
> http://marc.theaimsgroup.com/?l=linux-ia64&m=108189860401704&w=2
> 
> Hugetlb demand paging has been part of SuSE SLES 9 for awhile now
> and this patchset is intended to help hugetlb demand paging also get
> into the official Linux kernel. Huge pages are referred to as
> "compound" pages in terms of "struct page" in the Linux kernel. The
> term "compund page" may be used alternatively to huge page.

I wish we could start calling this "lazy allocation" instead of
"demand paging".  "Demand paging" makes people think of swapping
hugepages, or mapping files on real filesystems with hugepages, which
is not what these patches do, and probably something we don't want to
do.

-- 
David Gibson			| For every complex problem there is a
david AT gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.
http://www.ozlabs.org/people/dgibson

  parent reply	other threads:[~2004-10-27  5:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B05667366EE6204181EABE9C1B1C0EB504BFA47C@scsmsx401.amr.corp.intel.com>
2004-10-26  1:26 ` Hugepages demand paging V2 [0/8]: Discussion and overview Christoph Lameter
2004-10-26  1:27   ` Hugepages demand paging V2 [1/8]: hugetlb fault handler Christoph Lameter
2005-01-18 12:21     ` Hirokazu Takahashi
2005-01-18 16:33       ` Christoph Lameter
2004-10-26  1:28   ` Hugepages demand paging V2 [2/8]: allocation control Christoph Lameter
2004-10-26  1:28   ` Hugepages demand paging V2 [3/8]: simple numa compatible allocator Christoph Lameter
2005-02-02 12:21     ` Hirokazu Takahashi
2004-10-26  1:29   ` Hugepages demand paging V2 [4/8]: ia64 arch modifications Christoph Lameter
2004-10-26  1:29   ` Hugepages demand paging V2 [5/8]: i386 " Christoph Lameter
2004-10-26  1:30   ` Hugepages demand paging V2 [6/8]: sparc64 " Christoph Lameter
2004-10-26  1:31   ` Hugepages demand paging V2 [7/8]: sh64 " Christoph Lameter
2004-10-26  1:31   ` Hugepages demand paging V2 [8/8]: sh arch specific modifications Christoph Lameter
2004-10-26  2:23   ` Hugepages demand paging V2 [0/8]: Discussion and overview William Lee Irwin III
2004-10-26  2:40     ` Jesse Barnes
2004-10-26  2:43       ` William Lee Irwin III
2004-10-26 14:35       ` Robin Holt
2004-10-26 16:44         ` Jesse Barnes
2004-10-26 17:40           ` William Lee Irwin III
2004-10-26 17:45             ` Christoph Lameter
2004-10-26 17:47               ` William Lee Irwin III
2004-10-27 18:06         ` Christoph Lameter
2004-10-27 23:01           ` Ray Bryant
2004-10-28 11:51             ` Robin Holt
2004-10-28 16:34               ` Ray Bryant
2004-10-27 23:08           ` Ray Bryant
2004-10-27  5:23   ` David Gibson [this message]
2004-10-27 16:25     ` Christoph Lameter
2004-10-27  6:48   ` William Lee Irwin III
2004-10-27 14:21     ` Ray Bryant
2004-10-27 16:30     ` 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=20041027052317.GG1676@zax \
    --to=david@gibson.dropbear.id.au \
    --cc=clameter@sgi.com \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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