public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
	        John Reiser <jreiser@bitwagon.com>,
	binutils@sourceware.org
Subject: Re: Help needed to track down bug: linking Linux kernel with gold  creates unbootable kernel
Date: Fri, 23 Apr 2010 01:21:00 -0000	[thread overview]
Message-ID: <mcrbpdbx8tc.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <x2h6dc9ffc81004221723n6151420and3cb9d57df211f31@mail.gmail.com> (H. J. Lu's message of "Thu\, 22 Apr 2010 17\:23\:55 -0700")

"H.J. Lu" <hjl.tools@gmail.com> writes:

> 2MB maximum page size may have a bigger gap between PT_LOAD
> segment in memory than 4KB maximum page size. But it doesn't necessarily
> use more memory nor disk space. Since x86_64 is 64bit, address
> space shouldn't be an issue in vast majority cases. I'd like to hear
> a case to say otherwise.

The increased use of address space was an issue with x86_64 binaries
which opened hundreds of shared libraries.  Each shared library was
burning 2 megabytes of address space between the text and data
segments.  This in turn caused trouble with setting limits on the
amount of virtual memory which could be allocated: greatly increasing
the limits to permit hundreds of shared libraries meant that the
limits were unreasonably high for programs with only a couple of
shared libraries.  This was a problem we found with GNU ld a while
back.  While other workarounds were possible, using -z max-page-size
was a simple one.  I didn't see any reason to carry that problem
forward with gold, given that extremely few programs need -z
max-page-size larger than 0x1000 on x86_64.

Ian

  reply	other threads:[~2010-04-23  1:21 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 19:25 Török Edwin
2010-04-09 22:24 ` Ian Lance Taylor
2010-04-09 22:52   ` Doug Kwan (關振德)
2010-04-10 12:52   ` Török Edwin
2010-04-11 18:25     ` John Reiser
2010-04-12  9:39       ` Török Edwin
2010-04-12 15:17         ` John Reiser
2010-04-12 18:52           ` Török Edwin
2010-04-12 20:49             ` John Reiser
2010-04-13  5:27       ` Ian Lance Taylor
2010-04-22 21:10         ` H.J. Lu
2010-04-22 21:21           ` H.J. Lu
2010-04-22 21:27             ` Suresh Siddha
2010-04-23  0:00             ` Ian Lance Taylor
2010-04-23  0:24               ` H.J. Lu
2010-04-23  1:21                 ` Ian Lance Taylor [this message]
2010-04-23  1:46                   ` H.J. Lu
2010-04-23  1:58                     ` David Miller
2010-04-23  2:38                       ` H.J. Lu
2010-04-23  3:05                       ` Ian Lance Taylor
2010-04-23  4:27                         ` H.J. Lu
2010-04-22 21:25           ` John Reiser
2010-04-23  4:49             ` gold patch committed (Was: Re: Help needed to track down bug: linking Linux kernel with gold creates unbootable kernel) Ian Lance Taylor
2010-04-23 12:44               ` H.J. Lu
2010-04-23 14:12                 ` Ian Lance Taylor
2010-04-23 14:35                   ` H.J. Lu
2010-04-23 14:43                     ` Ian Lance Taylor
2010-04-23 14:47                       ` H.J. Lu
2010-04-23 15:31                         ` Ian Lance Taylor
2010-04-23 15:39                           ` H.J. Lu
2010-04-23 14:44                     ` H.J. Lu
2010-04-23 15:16                       ` Ian Lance Taylor
2010-04-23 15:30                         ` H.J. Lu
2010-04-23 15:50                           ` Ian Lance Taylor
2010-04-23 17:57                             ` H.J. Lu
2010-04-23 15:55                           ` John Reiser
2010-04-23 14:40                   ` John Reiser
2010-04-23 14:02               ` Török Edwin
2010-04-23 14:48                 ` H.J. Lu
2010-04-23 14:51                   ` Török Edwin
2010-04-23 23:30                 ` Ian Lance Taylor
2010-04-24  7:29                   ` Török Edwin
2010-04-22 23:57           ` Help needed to track down bug: linking Linux kernel with gold creates unbootable kernel Ian Lance Taylor
2010-04-12 17:48     ` Ian Lance Taylor
2010-04-12 18:04       ` Török Edwin

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=mcrbpdbx8tc.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
    --to=iant@google.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=jreiser@bitwagon.com \
    --cc=suresh.b.siddha@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).