From: Ralf Baechle <ralf@linux-mips.org>
To: Dajie Tan <jiankemeng@gmail.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: [PATCH] 16K page size in 32 bit kernel
Date: Tue, 31 Jul 2007 11:00:27 +0100 [thread overview]
Message-ID: <20070731100027.GA3983@linux-mips.org> (raw)
In-Reply-To: <20070731130950.GA5540@sw-linux.com>
On Tue, Jul 31, 2007 at 05:09:51PM +0400, Dajie Tan wrote:
> 32-bit Kernel for loongson2e currently use 16KB page size to avoid
> cache alias problem.So, the definiton of PGDIR_SHIFT muse be 12+14.
>
> Using 22 in 16K page size do not lead to a serious problem but the number
> of pages allocated for page table is more than previous. (cat
> /proc/vmstat | grep nr_page_table_pages)
>
> It's been tested on FuLong mini PC(loongson2e inside).
Looking good, applied. Thanks!
Did by coincidence any of you try 64K pages with a 32-bit kernel?
Ralf
next prev parent reply other threads:[~2007-07-31 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 13:09 [PATCH] 16K page size in 32 bit kernel Dajie Tan
2007-07-31 9:37 ` Songmao Tian
2007-07-31 9:37 ` Songmao Tian
2007-07-31 10:00 ` Ralf Baechle [this message]
2007-07-31 13:49 ` Songmao Tian
2007-07-31 20:45 ` Ralf Baechle
2007-08-01 0:47 ` Songmao Tian
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=20070731100027.GA3983@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=jiankemeng@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox