From: zhong jiang <zhongjiang@huawei.com>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
akpm@linux-foundation.org, linux-mm <linux-mm@kvack.org>,
Saeed Mahameed <saeedm@mellanox.com>,
Tariq Toukan <tariqt@mellanox.com>
Subject: Re: Page allocator order-0 optimizations merged
Date: Tue, 11 Apr 2017 09:54:39 +0800 [thread overview]
Message-ID: <58EC375F.5040800@huawei.com> (raw)
In-Reply-To: <20170410151051.n4lytmha4tqh4l3t@techsingularity.net>
On 2017/4/10 23:10, Mel Gorman wrote:
> On Mon, Apr 10, 2017 at 10:31:48PM +0800, zhong jiang wrote:
>> Hi, Mel
>>
>> The patch I had test on arm64. I find the great degradation. I test it by micro-bench.
>> The patrly data is as following. and it is stable. That stands for the allocate and free time.
>>
> What type of allocations is the benchmark doing? In particular, what context
> is the microbenchmark allocating from? Lastly, how did you isolate the
> patch, did you test two specific commits in mainline or are you comparing
> 4.10 with 4.11-rcX?
>
Hi, Mel
benchmark adopt 0 order allocation. just insmod module allocate memory by alloc_pages.
it is not interrupt context. I test the patch in linux 4.1 stable. In x86 , it have 10% improve.
but in arm64, it have great degradation.
Thanks
zhongjiang
--
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>
prev parent reply other threads:[~2017-04-11 2:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58b48b1f.F/jo2/WiSxvvGm/z%akpm@linux-foundation.org>
2017-03-01 13:48 ` Jesper Dangaard Brouer
2017-03-01 17:36 ` Tariq Toukan
2017-03-22 17:39 ` Tariq Toukan
2017-03-22 23:40 ` Mel Gorman
2017-03-23 13:43 ` Jesper Dangaard Brouer
2017-03-23 14:51 ` Mel Gorman
2017-03-26 8:21 ` Tariq Toukan
2017-03-26 10:17 ` Tariq Toukan
2017-03-27 7:32 ` Pankaj Gupta
2017-03-27 8:55 ` Jesper Dangaard Brouer
2017-03-27 12:28 ` Mel Gorman
2017-03-27 12:39 ` Jesper Dangaard Brouer
2017-03-27 13:32 ` Mel Gorman
2017-03-28 7:32 ` Tariq Toukan
2017-03-28 8:29 ` Jesper Dangaard Brouer
2017-03-28 16:05 ` Tariq Toukan
2017-03-28 18:24 ` Jesper Dangaard Brouer
2017-03-29 7:13 ` Tariq Toukan
2017-03-28 8:28 ` Pankaj Gupta
2017-03-27 14:15 ` Matthew Wilcox
2017-03-27 15:15 ` Jesper Dangaard Brouer
2017-03-27 16:58 ` in_irq_or_nmi() Matthew Wilcox
2017-03-29 8:12 ` in_irq_or_nmi() Peter Zijlstra
2017-03-29 8:59 ` in_irq_or_nmi() Jesper Dangaard Brouer
2017-03-29 9:19 ` in_irq_or_nmi() Peter Zijlstra
2017-03-29 18:12 ` in_irq_or_nmi() Matthew Wilcox
2017-03-29 19:11 ` in_irq_or_nmi() Jesper Dangaard Brouer
2017-03-29 19:44 ` in_irq_or_nmi() and RFC patch Jesper Dangaard Brouer
2017-03-30 6:49 ` Peter Zijlstra
2017-03-30 7:12 ` Jesper Dangaard Brouer
2017-03-30 7:35 ` Peter Zijlstra
2017-03-30 9:46 ` Jesper Dangaard Brouer
2017-03-30 13:04 ` Mel Gorman
2017-03-30 15:07 ` Jesper Dangaard Brouer
2017-04-03 12:05 ` Mel Gorman
2017-04-05 8:53 ` Mel Gorman
2017-04-10 14:31 ` Page allocator order-0 optimizations merged zhong jiang
2017-04-10 15:10 ` Mel Gorman
2017-04-11 1:54 ` zhong jiang [this message]
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=58EC375F.5040800@huawei.com \
--to=zhongjiang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=brouer@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=tariqt@mellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox