public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "J.C. Pizarro" <jcpiza@gmail.com>
Cc: David Miller <davem@davemloft.net>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: larger default page sizes...
Date: Wed, 26 Mar 2008 08:57:47 -0700	[thread overview]
Message-ID: <47EA727B.8090606@zytor.com> (raw)
In-Reply-To: <998d0e4a0803251647i2abefe96t34ec4ad6706afcfd@mail.gmail.com>

J.C. Pizarro wrote:
> 
> But there is a general problem of larger pages in systems that
> don't support them natively (in hardware) depending in how it's
> implemented the memory manager in the kernel:
> 
>    "Doubling the soft page size implies
>       halfing the TLB soft-entries in the old hardware".
> 
>    "x4 soft page size=> 1/4 TLB soft-entries, ... and so on."
> 
> Assuming one soft double-sized page represents 2 real-sized pages,
> one replacing of one soft double-sized page implies replacing
> 2 TLB's entries containing the 2 real-sized pages.
> 
> The TLB is very small, its entries are around 24 entries aprox. in
> some processors!.
> 

That's not a problem, actually, since the TLB entries can get shuffled 
like any other (for software TLBs it's a little different, but it can be 
dealt with there too.)

The *real* problem is ABI breakage.

	-hpa

  reply	other threads:[~2008-03-26 15:58 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 23:47 larger default page sizes J.C. Pizarro
2008-03-26 15:57 ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-21 17:40 [11/14] vcompound: Fallbacks for order 1 stack allocations on IA64 and x86 Christoph Lameter
2008-03-21 21:57 ` David Miller
2008-03-24 18:27   ` 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
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

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=47EA727B.8090606@zytor.com \
    --to=hpa@zytor.com \
    --cc=davem@davemloft.net \
    --cc=jcpiza@gmail.com \
    --cc=linux-kernel@vger.kernel.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