From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-mm@kvack.org
Subject: Re: isolate_freepages_block(): very high intermittent overhead
Date: Tue, 28 Oct 2014 09:59:16 +0100 [thread overview]
Message-ID: <20141028085916.GA337@x4> (raw)
In-Reply-To: <544EC0C5.7050808@suse.cz>
On 2014.10.27 at 23:01 +0100, Vlastimil Babka wrote:
> On 10/27/2014 09:40 PM, Markus Trippelsdorf wrote:
> > On my v3.18-rc2 kernel isolate_freepages_block() sometimes shows up very
> > high (>20%) in perf top during the configuration phase of software
> > builds. It increases build time considerably.
> >
> > Unfortunately the issue is not 100% reproducible, because it appears
> > only intermittently. And the symptoms vanish after a few minutes.
>
> Does it happen for long enough so you can capture it by perf record -g ?
It only happens when I use the "Lockless Allocator":
http://locklessinc.com/downloads/lockless_allocator_src.tgz
I use: LD_PRELOAD=/usr/lib/libllalloc.so.1.3 when building software,
because it gives me a ~8% speed boost over glibc's malloc.
Unfortunately, I don't have time to debug this further and have disabled
"Transparent Hugepage Support" for now.
--
Markus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-10-28 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 20:40 isolate_freepages_block(): very high intermittent overhead Markus Trippelsdorf
2014-10-27 21:06 ` Markus Trippelsdorf
2014-10-27 22:01 ` Vlastimil Babka
2014-10-28 8:59 ` Markus Trippelsdorf [this message]
2014-10-29 15:08 ` Vlastimil Babka
2014-11-06 11:42 ` Vlastimil Babka
2014-11-06 11:53 ` Markus Trippelsdorf
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=20141028085916.GA337@x4 \
--to=markus@trippelsdorf.de \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
/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 NNTP newsgroup(s).