All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: lkp@lists.01.org
Subject: Re: hugepage compaction causes performance drop
Date: Fri, 20 Nov 2015 16:55:01 +0800	[thread overview]
Message-ID: <564EDFE5.5010709@intel.com> (raw)
In-Reply-To: <564DCEA6.3000802@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]

On 11/19/2015 09:29 PM, Vlastimil Babka wrote:
> +CC Andrea, David, Joonsoo
> 
> On 11/19/2015 10:29 AM, Aaron Lu wrote:
>> The vmstat and perf-profile are also attached, please let me know if you
>> need any more information, thanks.
> 
> Output from vmstat (the tool) isn't much useful here, a periodic "cat 
> /proc/vmstat" would be much better.

No problem.

> The perf profiles are somewhat weirdly sorted by children cost (?), but 
> I noticed a very high cost (46%) in pageblock_pfn_to_page(). This could 
> be due to a very large but sparsely populated zone. Could you provide 
> /proc/zoneinfo?

Is a one time /proc/zoneinfo enough or also a periodic one?

> If the compaction scanners behave strangely due to a bug, enabling the 
> ftrace compaction tracepoints should help find the cause. That might 
> produce a very large output, but maybe it would be enough to see some 
> parts of it (i.e. towards beginning, middle, end of the experiment).

I'll see how to do this, never used ftrace before.

Thanks for the quick response.

Regards,
Aaron

WARNING: multiple messages have this Message-ID (diff)
From: Aaron Lu <aaron.lu@intel.com>
To: Vlastimil Babka <vbabka@suse.cz>, linux-mm@kvack.org
Cc: 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>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: hugepage compaction causes performance drop
Date: Fri, 20 Nov 2015 16:55:01 +0800	[thread overview]
Message-ID: <564EDFE5.5010709@intel.com> (raw)
In-Reply-To: <564DCEA6.3000802@suse.cz>

On 11/19/2015 09:29 PM, Vlastimil Babka wrote:
> +CC Andrea, David, Joonsoo
> 
> On 11/19/2015 10:29 AM, Aaron Lu wrote:
>> The vmstat and perf-profile are also attached, please let me know if you
>> need any more information, thanks.
> 
> Output from vmstat (the tool) isn't much useful here, a periodic "cat 
> /proc/vmstat" would be much better.

No problem.

> The perf profiles are somewhat weirdly sorted by children cost (?), but 
> I noticed a very high cost (46%) in pageblock_pfn_to_page(). This could 
> be due to a very large but sparsely populated zone. Could you provide 
> /proc/zoneinfo?

Is a one time /proc/zoneinfo enough or also a periodic one?

> If the compaction scanners behave strangely due to a bug, enabling the 
> ftrace compaction tracepoints should help find the cause. That might 
> produce a very large output, but maybe it would be enough to see some 
> parts of it (i.e. towards beginning, middle, end of the experiment).

I'll see how to do this, never used ftrace before.

Thanks for the quick response.

Regards,
Aaron

--
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>

  reply	other threads:[~2015-11-20  8:55 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 [this message]
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
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=564EDFE5.5010709@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.