From: "H. J. Lu" <hjl@lucon.org>
To: binutils@sources.redhat.com
Cc: discuss@x86-64.org
Subject: RFC: Change x86-64 maximum page size to 2MB
Date: Wed, 17 May 2006 11:24:00 -0000 [thread overview]
Message-ID: <20060516232326.GA18996@lucon.org> (raw)
The current x86-64 maximum page size is 1MB. With the future
development, 2MB is better for performance. Using 2MB won't break
anything, except for up to 2MB gap in virtual address space per file,
instead of 1MB. x86-64 has 48 bits in virtual address space. It
shouldn't be an issue for most applications. I have a patch:
http://sourceware.org/ml/binutils/2005-05/msg00644.html
which can be used to implement "-z max-page-size=xxxx" so that people
can control maximum page size at the link time if they prefer different
maximum page size.
H.J.
next reply other threads:[~2006-05-16 23:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 11:24 H. J. Lu [this message]
2006-05-19 12:39 ` Nick Clifton
2006-05-22 23:57 ` H. J. Lu
2006-05-24 7:24 ` PATCH: Add "-z max-page-size=xxxx"/"-z common-page-size=xxxx" H. J. Lu
2006-05-31 11:36 ` Nick Clifton
2006-05-26 4:33 ` PATCH: Change x86-64 maximum page size to 2MB H. J. Lu
2006-05-26 21:48 ` Daniel Jacobowitz
2006-05-27 0:47 ` H. J. Lu
2006-05-27 16:33 ` H. J. Lu
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=20060516232326.GA18996@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=discuss@x86-64.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).