LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <ppc6dev@digitaldans.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: Scott Wood <scottwood@freescale.com>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>, Willy Tarreau <w@1wt.eu>
Subject: Re: [PATCH 0/3] 8xx: Large page(8MB) support for 2.4
Date: Mon, 10 Oct 2011 11:03:53 -0700	[thread overview]
Message-ID: <9CE82FAD-2451-4253-B304-CF8BE5AC8CAC@digitaldans.com> (raw)
In-Reply-To: <OFAF68F93F.57D058F1-ONC1257925.005B7C6F-C1257925.005C10D7@transmode.se>


On Oct 10, 2011, at 9:45 AM, Joakim Tjernlund wrote:

> That is an easy port but I will have to do that blind. Would you
> mind take this for a spin on 2.4 first?

My current system is running 2.6, so I don't have much
interested in testing 2.4

> The more interesting part is if one should use other sized(16K or  
> 512K) large pages too?

My thought long ago was most of the 8xx systems have rather small
real memories, so the larger pages, especially 512K may be too wasteful.
I've always been a fan of keeping the TLB handlers tiny and simple,
rather then spending the instructions doing complex replacements.
Remember, this also affects the I- and D-cache, so a more frequent
and trivial PTE update could very well gain larger system performance
than the management of larger pages with more complex code.
With all of the bug fix code in the handlers, maybe a larger page would
be better.

> Those should be useful for user space but it is a lot of work. I  
> haven't checked
> what large page support for user space is in 2.6 for ppc though.

The 2.6/3.0 kernel supports different, but fixed, page sizes.  IIRC,  
anything
over 64K may require distribution rebuilding to realign code/data  
sections
to more restrictive boundaries.  Maybe a 16K page would show some  
benefit.
I'll try to make some time to play with it.

Thanks.

	-- Dan

  reply	other threads:[~2011-10-10 18:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 11:38 [PATCH 0/3] 8xx: Large page(8MB) support for 2.4 Joakim Tjernlund
2011-10-10 11:38 ` [PATCH 1/3] 8xx: replace _PAGE_EXEC with _PAGE_PSE Joakim Tjernlund
2011-10-10 11:38 ` [PATCH 2/3] 8xx: Support LARGE pages in TLB code Joakim Tjernlund
2011-10-10 11:38 ` [PATCH 3/3] 8xx: Use LARGE pages for kernel RAM Joakim Tjernlund
2011-10-10 16:22 ` [PATCH 0/3] 8xx: Large page(8MB) support for 2.4 Dan Malek
2011-10-10 16:29   ` Willy Tarreau
2011-10-10 16:45   ` Joakim Tjernlund
2011-10-10 18:03     ` Dan Malek [this message]
2011-10-11  7:42       ` Joakim Tjernlund
     [not found]       ` <OF5A487DD5.BE515A85-ONC1257926.0029F008-C1257926.002A6323@LocalDomain>
2011-10-12 21:36         ` Joakim Tjernlund
2011-10-13  1:08           ` Dan Malek
2011-10-13 14:00             ` Joakim Tjernlund
2011-10-13 15:48               ` Dan Malek

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=9CE82FAD-2451-4253-B304-CF8BE5AC8CAC@digitaldans.com \
    --to=ppc6dev@digitaldans.com \
    --cc=joakim.tjernlund@transmode.se \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=w@1wt.eu \
    /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