From: Ralf Baechle <ralf@linux-mips.org>
To: Jonathan Day <imipak@yahoo.com>
Cc: Thiemo Seufer <ths@networkno.de>,
Peter Watkins <treestem@gmail.com>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] 64K page size
Date: Tue, 29 Aug 2006 15:07:00 +0100 [thread overview]
Message-ID: <20060829140700.GD29289@linux-mips.org> (raw)
In-Reply-To: <20060823162324.43027.qmail@web31507.mail.mud.yahoo.com>
On Wed, Aug 23, 2006 at 09:23:24AM -0700, Jonathan Day wrote:
> I am extremely interested in big pages (64K, etc), and
> the sooner the better. If there is anything not
> considered OK for immediate inclusion in the Linux
> MIPS git tree, I would love to have a copy anyway.
> Large pages will be necessary for some high-priority
> work I'm doing, although stability at this point seems
> to be an optional extra. (Hence why the patches are
> much more important than whether they're actually
> finished yet.)
We're getting very close to a 2.6.18 release and 64kB pages are still
quite experimental, so I'm putting all the 64kB pagesize related fixes
into the queue branch. 16kB by now has a few users, so I give it
higher priority.
I've been promised hugetlbfs since quite a while but that somehow never
materialized. Or maybe that's just because the runtime generated TLB
exception handlers killed the patches ;-)
Ralf
next prev parent reply other threads:[~2006-08-29 14:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 15:15 [PATCH] 64K page size Peter Watkins
2006-08-23 16:00 ` Thiemo Seufer
2006-08-23 16:23 ` Jonathan Day
2006-08-23 17:53 ` Thiemo Seufer
2006-08-25 0:28 ` Ralf Baechle
2006-08-25 5:11 ` Jonathan Day
2006-08-29 14:07 ` Ralf Baechle [this message]
2006-08-31 3:48 ` Yoichi Yuasa
2006-08-31 21:24 ` Ralf Baechle
2006-08-29 13:50 ` Ralf Baechle
2006-08-31 15:12 ` Peter Watkins
2006-08-29 14:01 ` Ralf Baechle
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=20060829140700.GD29289@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=imipak@yahoo.com \
--cc=linux-mips@linux-mips.org \
--cc=ths@networkno.de \
--cc=treestem@gmail.com \
/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