public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/50636] GC in large LTO builds cause excessive fragmentation in memory map Date: Thu, 06 Oct 2011 21:47:00 -0000 [thread overview] Message-ID: <bug-50636-4-n5gFFgUera@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50636-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50636 --- Comment #5 from Andi Kleen <andi-gcc at firstfloor dot org> 2011-10-06 21:46:32 UTC --- If it's a 2MB page then madvise MADV_DONTNEED will split it if it's not 2MB aligned. It would be good to optimize the freeing pattern so that this happens rarely. I will try to do some numbers how much 2MB pages improves performance. If yes we could also do a MADV_HUGEPAGE by default. But short term fix would be simply to have a threshold for freepages before freeing?
next prev parent reply other threads:[~2011-10-06 21:47 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-06 18:21 [Bug other/50636] New: " andi-gcc at firstfloor dot org 2011-10-06 19:20 ` Jan Hubicka 2011-10-06 19:21 ` [Bug other/50636] " hubicka at ucw dot cz 2011-10-06 21:29 ` jakub at gcc dot gnu.org 2011-10-06 21:32 ` andi-gcc at firstfloor dot org 2011-10-06 21:42 ` jakub at gcc dot gnu.org 2011-10-06 21:47 ` andi-gcc at firstfloor dot org [this message] 2011-10-07 5:49 ` andi-gcc at firstfloor dot org 2011-10-07 5:51 ` andi-gcc at firstfloor dot org 2011-10-07 8:25 ` rguenth at gcc dot gnu.org 2011-10-07 10:01 ` jakub at gcc dot gnu.org 2011-10-07 14:45 ` andi-gcc at firstfloor dot org 2011-10-08 16:48 ` andi-gcc at firstfloor dot org 2011-10-08 19:55 ` andi-gcc at firstfloor dot org 2011-10-08 20:14 ` jakub at gcc dot gnu.org 2011-10-08 21:10 ` andi-gcc at firstfloor dot org 2011-10-17 14:44 ` ak at gcc dot gnu.org 2011-10-20 0:11 ` andi-gcc at firstfloor dot org
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=bug-50636-4-n5gFFgUera@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).