From: "Donny Cooper" <dcooper@atcc.necsys.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] IA64 Linux Kernel Page Sizes
Date: Thu, 06 Sep 2001 16:22:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805131@msgid-missing> (raw)
(1) Below is a previous mail, from David M., responding to page size questions for IA64 kernels.
> As for the future: I'd like to start playing with superpage support
> fairly soon (once I get some spare time on my hands... ;-). With
> superpages, physically contiguous regions of memory could be mapped
> with a single TLB entry, giving you most of the benefit of (very)
> large page sizes. --david
Are there any updates on these plans?
(2) Below are current available kernel options (from config).
4KB For best IA-32 compatibility
8KB For best IA-64 performance
16KB For best IA-64 performance
64KB Not for Itanium.
What is "IA64 best performance" based on?
We have a large memory system (32GB), and are not concerned with wasting memory during certain benchmarks. Are 64KB
pages truly not functional on Itanium, or just not recommended because of memory waste. To my knowledge, HP-UX seems to
benefit from 64KB pages on ITANIUM.
Any input or recommendation on these items is appreciated.
Thanks.
-----------------------------------
Donny Cooper
NEC Systems, Inc.
Advanced Technical Computing Center
dcooper@atcc.necsys.com
www.necservers.com
-----------------------------------
next reply other threads:[~2001-09-06 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 16:22 Donny Cooper [this message]
2001-09-06 18:19 ` [Linux-ia64] IA64 Linux Kernel Page Sizes David Mosberger
2001-09-07 17:01 ` Seth, Rohit
2001-09-10 20:31 ` Erich Focht
2001-09-10 22:48 ` Seth, Rohit
2001-09-11 9:35 ` Christoph Hellwig
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=marc-linux-ia64-105590698805131@msgid-missing \
--to=dcooper@atcc.necsys.com \
--cc=linux-ia64@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