All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: 林建安 <colin@realtek.com.tw>
Cc: linux-mips@linux-mips.org
Subject: Re: The impact to change page size to 16k for cache alias
Date: Mon, 30 Mar 2009 10:55:13 +0200	[thread overview]
Message-ID: <20090330085512.GA10301@linux-mips.org> (raw)
In-Reply-To: <9BDA961341E843F29C1C1ECDB54FD0CF@realtek.com.tw>

On Mon, Mar 30, 2009 at 12:06:51PM +0800, 林建安 wrote:

> Hi all,
> We are willing to use 16k page size to avoid cache alias problem.
> The Linux version we use is 2.6.12. If we just upgrade mm system to 
> support 16k page size, what else problems will happen?
> There is already one thing we know that applications of ELF format  
> applications should be transformed to be 16k alignment.
> Another one, we think, highly suspected to be problematic is that many  
> drivers will be ok for 4k page size but fails for 16k.
> That is because 4k page size had been seemed to be natural for a very 
> long long time.
> Any other problem that shall happen for 16k page size?

Most drivers are agnostic of the page size so no problems due to increased
page size are to be expected.

You will have to upgrade your kernel though.  There were some important
fixes for larger page size applied to later kernels.

  Ralf

  parent reply	other threads:[~2009-03-30  8:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30  4:06 The impact to change page size to 16k for cache alias 林建安
2009-03-30  4:06 ` 林建安
2009-03-30  8:24 ` Zhang Le
2009-03-31  8:11   ` Ralf Baechle
2009-03-31 16:54     ` Zhang Le
2009-03-31 17:12       ` Ralf Baechle
2009-03-31 18:09         ` Zhang Le
2009-03-30  8:55 ` Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-31 19:43 Peter Watkins

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=20090330085512.GA10301@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=colin@realtek.com.tw \
    --cc=linux-mips@linux-mips.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.