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/3] Free large chunks in ggc
Date: Sun, 23 Oct 2011 13:42:00 -0000 [thread overview]
Message-ID: <CAFiYyc0Zz32nOdoCkrctvYe20PkvscuUnH75AmFS-DLxH3c3DQ@mail.gmail.com> (raw)
In-Reply-To: <20111021183058.GC22535@one.firstfloor.org>
On Fri, Oct 21, 2011 at 8:30 PM, Andi Kleen <andi@firstfloor.org> wrote:
>> > diff --git a/gcc/ggc-page.c b/gcc/ggc-page.c
>> > index ba88e3f..eb0eeef 100644
>> > --- a/gcc/ggc-page.c
>> > +++ b/gcc/ggc-page.c
>> > @@ -972,6 +972,54 @@ release_pages (void)
>> > page_entry *p, *start_p;
>> > char *start;
>> > size_t len;
>> > + size_t mapped_len;
>> > + page_entry *next, *prev, *newprev;
>> > + size_t free_unit = PARAM_VALUE (GGC_FREE_UNIT) * G.pagesize;
>> > +
>> > + /* First free larger continuous areas to the OS.
>> > + This allows other allocators to grab these areas if needed.
>> > + This is only done on larger chunks to avoid fragmentation.
>> > + This does not always work because the free_pages list is only
>> > + sorted over a single GC cycle. */
>>
>> But release_pages is only called from ggc_collect, or what do you
>
> If there was a spike in GC usage and we end up with lots of free
> space in the free list afterward we free it back on the next GC cycle.
> Then if there's a malloc or other allocator later it can grab
> the address space we freed.
>
> That was done to address your earlier concern.
>
> This will only happen on ggc_collect of course.
>
> So one difference from before the madvise patch is that different
> generations of free pages can accumulate in the freelist. Before madvise
> the freelist would never contain more than one generation.
> Normally it's sorted by address due to the way GC works, but there's no
> attempt to keep the sort order over multiple generations.
>
> The "free in batch" heuristic requires sorting, so it will only
> work if all the pages are freed in a single gc cycle.
>
> I considered sorting, but it seemed to be too slow.
>
> I can expand the comment on that.
Ah, now I see ... but that's of course bad - I expect large regions to be
free only after multiple collections. Can you measure what sorting would
make for a difference?
>
>> mean with the above? Would the hitrate using the quire size increase
>> if we change how we allocate from the freelist or is it real fragmentation
>> that causes it?
>
> Not sure really about the hitrate. I haven't measured it. If hitrate
> was a concern the free list should be probably split into an array.
> I'm sure there are lots of other tunings that could be done on the GC,
> but probably not by me for now :)
Heh. Yeah, I suppose the freelist could be changed into a list of
allocation groups with free pages and a bitmap.
Richard.
>>
>> I'm a bit hesitant to approve the new param, I'd be ok if we just hard-code
>> quire-size / 2.
>
> Ok replacing it with a hardcoded value.
>
> -Andi
>
next prev parent reply other threads:[~2011-10-23 10:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 7:29 Updated ggc anti fragmentation patchkit Andi Kleen
2011-10-21 8:00 ` [PATCH 2/3] Free large chunks in ggc Andi Kleen
2011-10-21 10:39 ` Richard Guenther
2011-10-21 18:48 ` Andi Kleen
2011-10-23 13:42 ` Richard Guenther [this message]
2011-10-23 14:33 ` Richard Guenther
2011-10-23 20:03 ` Andi Kleen
2011-10-21 8:16 ` [PATCH 1/3] Add missing page rounding of a page_entry Andi Kleen
2011-10-21 10:04 ` Richard Guenther
2011-10-21 10:29 ` Jakub Jelinek
2011-10-21 18:08 ` Andi Kleen
2011-10-21 8:33 ` [PATCH 3/3] Add a fragmentation fallback in ggc-page Andi Kleen
2011-10-21 9:06 ` Jakub Jelinek
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=CAFiYyc0Zz32nOdoCkrctvYe20PkvscuUnH75AmFS-DLxH3c3DQ@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).