From: Sriraman Tallam <tmsriram@google.com>
To: binutils <binutils@sourceware.org>,
Ian Lance Taylor <iant@google.com>,
Cary Coutant <ccoutant@google.com>
Subject: Re: [patch] Gold linker patch to provide plugin support for mapping some text sections to an unique ELF segment.
Date: Tue, 31 Jul 2012 17:21:00 -0000 [thread overview]
Message-ID: <CAAs8Hmzm2GHJYRdPrbsOVa-Ude+q8LKquix0Wsi5B_7B3qy20w@mail.gmail.com> (raw)
In-Reply-To: <CAAs8Hmwvpta-SnSOeRORfnTa+qX-c3p+f3SQpGH8yZUhjf6SqA@mail.gmail.com>
Ping.
Thanks,
-Sri.
On Fri, Jul 20, 2012 at 5:28 PM, Sriraman Tallam <tmsriram@google.com> wrote:
> Hi,
>
> This patch allows plugins to specify that a subset of sections are
> to be mapped to an unique segment. This is useful, for instance, when
> a set of functions that are determined to be hot can be placed in an
> unique segment which can then be mapped to huge text pages. It has
> been found for some Google applications that mapping functions to huge
> pages, along with function layout, provides a significant performance
> benefit and this feature can take this further by only mapping certain
> functions to huge pages, which requires that they be placed in an
> unique segment.
>
> The plugin needs to specify a list of sections that have to mapped to
> an unique segment. The plugin can also specify any additional segment
> flags to be set. The segment flag bits 3 to 19 seem to be available
> and can be set to mark some segments which can later be mapped to huge
> pages. The flags which would be set by default, bits 0-2, cannot be
> unset by the plugin.
>
> Thoughts?
>
> Patch attached.
>
> Thanks,
> -Sri.
next prev parent reply other threads:[~2012-07-31 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 0:28 Sriraman Tallam
2012-07-31 17:21 ` Sriraman Tallam [this message]
2012-08-03 6:44 ` Cary Coutant
2012-08-10 0:56 ` Sriraman Tallam
2012-08-22 21:41 ` Ian Lance Taylor
2012-08-23 4:14 ` Sriraman Tallam
2012-08-24 17:41 ` Ian Lance Taylor
2012-08-24 17:44 ` Cary Coutant
2012-08-24 19:01 ` Sriraman Tallam
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=CAAs8Hmzm2GHJYRdPrbsOVa-Ude+q8LKquix0Wsi5B_7B3qy20w@mail.gmail.com \
--to=tmsriram@google.com \
--cc=binutils@sourceware.org \
--cc=ccoutant@google.com \
--cc=iant@google.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).