public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <richard.guenther@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: gcc-patches@gcc.gnu.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 2/5] Increase the GGC quite size to 2MB
Date: Mon, 10 Oct 2011 10:21:00 -0000	[thread overview]
Message-ID: <CAFiYyc0LzPYBxqiiaCji+CH9Raiq=05iw+zn6xmvEFGjh2KbvQ@mail.gmail.com> (raw)
In-Reply-To: <1318190141-1220-3-git-send-email-andi@firstfloor.org>

On Sun, Oct 9, 2011 at 9:55 PM, Andi Kleen <andi@firstfloor.org> wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> Using 2MB allows modern kernels to use 2MB huge pages on x86.

Ok.

Thanks,
Richard.

> gcc/:
>
> 2011-10-08   Andi Kleen <ak@linux.intel.com>
>
>        * ggc-page.c (GGC_QUIRE_SIZE): Increase to 512
> ---
>  gcc/ggc-page.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/gcc/ggc-page.c b/gcc/ggc-page.c
> index b0b3b3f..1f52b56 100644
> --- a/gcc/ggc-page.c
> +++ b/gcc/ggc-page.c
> @@ -469,7 +469,7 @@ static struct globals
>    can override this by defining GGC_QUIRE_SIZE explicitly.  */
>  #ifndef GGC_QUIRE_SIZE
>  # ifdef USING_MMAP
> -#  define GGC_QUIRE_SIZE 256
> +#  define GGC_QUIRE_SIZE 512   /* 2MB for 4K pages */
>  # else
>  #  define GGC_QUIRE_SIZE 16
>  # endif
> --
> 1.7.5.4
>
>

  reply	other threads:[~2011-10-10 10:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 19:56 Improve ggc-page fragmentation Andi Kleen
2011-10-09 19:56 ` [PATCH 3/5] On a Linux kernel ask explicitely for a huge page in ggc Andi Kleen
2011-10-10 10:17   ` Richard Guenther
2011-10-10 10:34     ` Jakub Jelinek
2011-10-10 14:04       ` Andi Kleen
2011-10-10 13:54     ` Andi Kleen
2011-10-09 19:56 ` [PATCH 5/5] Add error checking to lto_section_read Andi Kleen
2011-10-10 10:25   ` Richard Guenther
2011-10-09 19:56 ` [PATCH 2/5] Increase the GGC quite size to 2MB Andi Kleen
2011-10-10 10:21   ` Richard Guenther [this message]
2011-10-10 13:58   ` Jan Hubicka
2011-10-09 20:09 ` [PATCH 4/5] Add a freeing threshold for the garbage collector Andi Kleen
2011-10-10 10:29   ` Richard Guenther
2011-10-10 14:06     ` Andi Kleen
2011-10-10 14:59       ` Richard Guenther
2011-10-09 22:18 ` [PATCH 1/5] Use MADV_DONTNEED for freeing in " Andi Kleen
2011-10-10 10:33   ` Richard Guenther
2011-10-10 10:48     ` Jakub Jelinek
2011-10-10 11:21       ` Richard Guenther
2011-10-10 11:58         ` Jakub Jelinek
2011-10-10 14:23     ` Andi Kleen
2011-10-10 15:05       ` Richard Guenther
2011-10-10 18:09         ` Andi Kleen
2011-10-16  9:04   ` Andi Kleen
2011-10-16 11:29     ` Richard Guenther
2011-10-16 19:38       ` Andi Kleen
2011-10-17  8:41         ` Richard Guenther

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='CAFiYyc0LzPYBxqiiaCji+CH9Raiq=05iw+zn6xmvEFGjh2KbvQ@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=gcc-patches@gcc.gnu.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).