From: Marc Duponcheel <marc@offline.be>
To: David Rientjes <rientjes@google.com>
Cc: Mel Gorman <mgorman@suse.de>,
Andy Lutomirski <luto@amacapital.net>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Marc Duponcheel <marc@offline.be>
Subject: Re: [3.6 regression?] THP + migration/compaction livelock (I think)
Date: Sat, 17 Nov 2012 01:18:26 +0100 [thread overview]
Message-ID: <20121117001826.GC9816@offline.be> (raw)
In-Reply-To: <20121115011449.GA20858@offline.be>
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
Hi David, others
Results seem OK
recap: I have 2 6core 64bit opterons and I make -j13
I do
# echo always >/sys/kernel/mm/transparent_hugepage/enabled
# while [ 1 ]
do
sleep 10
date
echo = vmstat
egrep "(thp|compact)" /proc/vmstat
echo = khugepaged stack
cat /proc/501/stack
done > /tmp/49361.xxxx
# emerge icedtea
(where 501 = pidof khugepaged)
for xxxx = base = 3.6.6
and xxxx = test = 3.6.6 + diff you provided
I attach
/tmp/49361.base.gz
and
/tmp/49361.test.gz
Note:
with xxx=base, I could see
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8617 root 20 0 3620m 41m 10m S 988.3 0.5 6:19.06 javac
1 root 20 0 4208 588 556 S 0.0 0.0 0:03.25 init
already during configure and I needed to kill -9 javac
with xxx=test, I could see
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9275 root 20 0 2067m 474m 10m S 304.2 5.9 0:32.81 javac
710 root 0 -20 0 0 0 S 0.3 0.0 0:01.07 kworker/0:1H
later when processing >700 java files
Also note that with xxx=test compact_blocks_moved stays 0
hope this helps
Thanks
have a nice day
On 2012 Nov 15, Marc Duponcheel wrote:
> Hi David
>
> Thanks for the changeset
>
> I will test 3.6.6 without&with this weekend.
>
> Have a nice day
--
Marc Duponcheel
Velodroomstraat 74 - 2600 Berchem - Belgium
+32 (0)478 68.10.91 - marc@offline.be
[-- Attachment #2: 49361.base.gz --]
[-- Type: application/octet-stream, Size: 861 bytes --]
[-- Attachment #3: 49361.test.gz --]
[-- Type: application/octet-stream, Size: 691 bytes --]
next prev parent reply other threads:[~2012-11-17 0:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 22:13 [3.6 regression?] THP + migration/compaction livelock (I think) Andy Lutomirski
2012-11-13 22:13 ` Andy Lutomirski
2012-11-13 23:11 ` David Rientjes
2012-11-13 23:11 ` David Rientjes
2012-11-13 23:25 ` Andy Lutomirski
2012-11-13 23:25 ` Andy Lutomirski
2012-11-13 23:41 ` David Rientjes
2012-11-13 23:41 ` David Rientjes
2012-11-13 23:45 ` Andy Lutomirski
2012-11-13 23:45 ` Andy Lutomirski
2012-11-13 23:54 ` David Rientjes
2012-11-13 23:54 ` David Rientjes
2012-11-14 1:22 ` Marc Duponcheel
2012-11-14 1:22 ` Marc Duponcheel
2012-11-14 1:51 ` David Rientjes
2012-11-14 1:51 ` David Rientjes
2012-11-14 13:21 ` Marc Duponcheel
2012-11-14 13:21 ` Marc Duponcheel
2012-11-14 10:01 ` Mel Gorman
2012-11-14 10:01 ` Mel Gorman
2012-11-14 13:29 ` Marc Duponcheel
2012-11-14 13:29 ` Marc Duponcheel
2012-11-14 21:50 ` David Rientjes
2012-11-14 21:50 ` David Rientjes
2012-11-15 1:14 ` Marc Duponcheel
2012-11-15 1:14 ` Marc Duponcheel
2012-11-17 0:18 ` Marc Duponcheel [this message]
2012-11-18 22:55 ` David Rientjes
2012-11-18 22:55 ` David Rientjes
2012-12-05 19:23 ` Andy Lutomirski
2012-12-05 19:23 ` Andy Lutomirski
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=20121117001826.GC9816@offline.be \
--to=marc@offline.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mgorman@suse.de \
--cc=rientjes@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.