From: Aaron Lu <aaron.lu@intel.com>
To: lkp@lists.01.org
Subject: Re: hugepage compaction causes performance drop
Date: Tue, 24 Nov 2015 11:40:28 +0800 [thread overview]
Message-ID: <5653DC2C.3090706@intel.com> (raw)
In-Reply-To: <CAAmzW4M6oJukBLwucByK89071RukF4UEyt02A7ZjenpPr5rsdQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
On 11/23/2015 05:24 PM, Joonsoo Kim wrote:
> 2015-11-23 17:33 GMT+09:00 Aaron Lu <aaron.lu@intel.com>:
>> On 11/23/2015 04:16 PM, Joonsoo Kim wrote:
>>>
>>> And, please attach always-always's vmstat numbers, too.
>>
>> Sure, attached the vmstat tool output, taken every second.
>
> Oops... I'd like to see '1 sec interval cat /proc/vmstat' for always-never.
Here it is, the proc-vmstat for always-never.
BTW, I'm still learning how to do proper ftrace for this case and it may
take a while.
Thanks,
Aaron
[-- Attachment #2: proc-vmstat.gz --]
[-- Type: application/gzip, Size: 17041 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Aaron Lu <aaron.lu@intel.com>
To: Joonsoo Kim <js1304@gmail.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>,
Linux Memory Management List <linux-mm@kvack.org>,
Huang Ying <ying.huang@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
lkp@lists.01.org, Andrea Arcangeli <aarcange@redhat.com>,
David Rientjes <rientjes@google.com>
Subject: Re: hugepage compaction causes performance drop
Date: Tue, 24 Nov 2015 11:40:28 +0800 [thread overview]
Message-ID: <5653DC2C.3090706@intel.com> (raw)
In-Reply-To: <CAAmzW4M6oJukBLwucByK89071RukF4UEyt02A7ZjenpPr5rsdQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
On 11/23/2015 05:24 PM, Joonsoo Kim wrote:
> 2015-11-23 17:33 GMT+09:00 Aaron Lu <aaron.lu@intel.com>:
>> On 11/23/2015 04:16 PM, Joonsoo Kim wrote:
>>>
>>> And, please attach always-always's vmstat numbers, too.
>>
>> Sure, attached the vmstat tool output, taken every second.
>
> Oops... I'd like to see '1 sec interval cat /proc/vmstat' for always-never.
Here it is, the proc-vmstat for always-never.
BTW, I'm still learning how to do proper ftrace for this case and it may
take a while.
Thanks,
Aaron
[-- Attachment #2: proc-vmstat.gz --]
[-- Type: application/gzip, Size: 17041 bytes --]
next prev parent reply other threads:[~2015-11-24 3:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 9:29 hugepage compaction causes performance drop Aaron Lu
2015-11-19 9:29 ` Aaron Lu
2015-11-19 13:29 ` Vlastimil Babka
2015-11-19 13:29 ` Vlastimil Babka
2015-11-20 8:55 ` Aaron Lu
2015-11-20 8:55 ` Aaron Lu
2015-11-20 9:33 ` Aaron Lu
2015-11-20 9:33 ` Aaron Lu
2015-11-20 10:06 ` Vlastimil Babka
2015-11-20 10:06 ` Vlastimil Babka
2015-11-23 8:16 ` Joonsoo Kim
2015-11-23 8:16 ` Joonsoo Kim
2015-11-23 8:33 ` Aaron Lu
2015-11-23 8:33 ` Aaron Lu
2015-11-23 9:24 ` Joonsoo Kim
2015-11-23 9:24 ` Joonsoo Kim
2015-11-24 3:40 ` Aaron Lu [this message]
2015-11-24 3:40 ` Aaron Lu
2015-11-24 4:55 ` Joonsoo Kim
2015-11-24 4:55 ` Joonsoo Kim
2015-11-24 7:27 ` Aaron Lu
2015-11-24 7:27 ` Aaron Lu
2015-11-24 8:29 ` Joonsoo Kim
2015-11-24 8:29 ` Joonsoo Kim
2015-11-25 12:44 ` Vlastimil Babka
2015-11-25 12:44 ` Vlastimil Babka
2015-11-26 5:47 ` Aaron Lu
2015-11-26 5:47 ` Aaron Lu
2015-11-24 2:45 ` Joonsoo Kim
2015-11-24 2:45 ` Joonsoo Kim
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=5653DC2C.3090706@intel.com \
--to=aaron.lu@intel.com \
--cc=lkp@lists.01.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 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.