public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: David Miller <davem@davemloft.net>
Cc: clameter@sgi.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	torvalds@linux-foundation.org
Subject: Re: larger default page sizes...
Date: Tue, 25 Mar 2008 11:50:00 +0000	[thread overview]
Message-ID: <18408.59112.945786.488350@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20080324.211532.33163290.davem@davemloft.net>

David Miller writes:

> From: Paul Mackerras <paulus@samba.org>
> Date: Tue, 25 Mar 2008 14:29:55 +1100
> 
> > The performance advantage of using hardware 64k pages is pretty
> > compelling, on a wide range of programs, and particularly on HPC apps.
> 
> Please read the rest of my responses in this thread, you
> can have your HPC cake and eat it too.

It's not just HPC, as I pointed out, it's pretty much everything,
including kernel compiles.  And "use hugepages" is a pretty inadequate
answer given the restrictions of hugepages and the difficulty of using
them.  How do I get gcc to use hugepages, for instance?  Using 64k
pages gives us a performance boost for almost everything without the
user having to do anything.

If the hugepage stuff was in a state where it enabled large pages to
be used for mapping an existing program, where possible, without any
changes to the executable, then I would agree with you.  But it isn't,
it's a long way from that, and (as I understand it) Linus has in the
past opposed the suggestion that we should move in that direction.

Paul.

  reply	other threads:[~2008-03-25 11:50 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080321061726.782068299@sgi.com>
     [not found] ` <20080321.002502.223136918.davem@davemloft.net>
     [not found]   ` <Pine.LNX.4.64.0803211037140.18671@schroedinger.engr.sgi.com>
     [not found]     ` <20080321.145712.198736315.davem@davemloft.net>
2008-03-24 18:27       ` [11/14] vcompound: Fallbacks for order 1 stack allocations on Christoph Lameter
2008-03-24 20:37         ` larger default page sizes David Miller
2008-03-24 21:05           ` Christoph Lameter
2008-03-24 21:43             ` David Miller
2008-03-25 17:48               ` Christoph Lameter
2008-03-25 23:22                 ` David Miller
2008-03-25 23:41                   ` Peter Chubb
2008-03-25 23:49                     ` David Miller
2008-03-26  0:25                       ` Peter Chubb
2008-03-26  0:31                         ` David Miller
2008-03-26  0:34                     ` David Mosberger-Tang
2008-03-26  0:39                       ` David Miller
2008-03-26  0:57                       ` Peter Chubb
2008-03-26  4:16                         ` John Marvin
2008-03-26  4:36                           ` David Miller
2008-03-24 21:25           ` Luck, Tony
2008-03-24 21:46             ` David Miller
2008-03-25  3:29           ` Paul Mackerras
2008-03-25  4:15             ` David Miller
2008-03-25 11:50               ` Paul Mackerras [this message]
2008-03-25 23:32                 ` David Miller
2008-03-25 23:49                   ` Luck, Tony
2008-03-26  0:16                     ` David Miller
2008-03-26 15:54                     ` Nish Aravamudan
2008-03-26 17:05                       ` Luck, Tony
2008-03-26 18:54                         ` Mel Gorman
2008-03-25 12:05             ` Andi Kleen
2008-03-25 21:27               ` Paul Mackerras
2008-03-26  5:24               ` Paul Mackerras
2008-03-26 15:59                 ` Linus Torvalds
2008-03-27  1:08                   ` Paul Mackerras
2008-03-26 17:56                 ` Christoph Lameter
2008-03-26 23:21                   ` David Miller
2008-03-27  3:00                   ` Paul Mackerras
2008-03-25 18:27             ` Dave Hansen
2008-03-24 21:13         ` [11/14] vcompound: Fallbacks for order 1 stack allocations on IA64 and x86 Luck, Tony
2008-03-25 17:42           ` [11/14] vcompound: Fallbacks for order 1 stack allocations on Christoph Lameter
2008-03-25 19:09             ` [11/14] vcompound: Fallbacks for order 1 stack allocations on IA64 and x86 Luck, Tony
2008-03-25 19:25               ` [11/14] vcompound: Fallbacks for order 1 stack allocations on 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=18408.59112.945786.488350@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=clameter@sgi.com \
    --cc=davem@davemloft.net \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@linux-foundation.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