[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9cf7f4c6-6dde-9dbb-cf93-7874437a442d@gmail.com>
Date: Fri, 25 Nov 2016 10:59:20 +1100
From: Balbir Singh <bsingharora@...il.com>
To: Zi Yan <zi.yan@...t.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Cc: akpm@...ux-foundation.org, minchan@...nel.org, vbabka@...e.cz,
mgorman@...hsingularity.net, kirill.shutemov@...ux.intel.com,
n-horiguchi@...jp.nec.com, khandual@...ux.vnet.ibm.com,
Zi Yan <zi.yan@...rutgers.edu>
Subject: Re: [PATCH 0/5] Parallel hugepage migration optimization
On 23/11/16 03:25, Zi Yan wrote:
> From: Zi Yan <zi.yan@...rutgers.edu>
>
> Hi all,
>
> This patchset boosts the hugepage migration throughput and helps THP migration
> which is added by Naoya's patches: https://lwn.net/Articles/705879/.
>
> Motivation
> ===============================
>
> In x86, 4KB page migrations are underutilizing the memory bandwidth compared
> to 2MB THP migrations. I did some page migration benchmarking on a two-socket
> Intel Xeon E5-2640v3 box, which has 23.4GB/s bandwidth, and discover
> there are big throughput gap, ~3x, between 4KB and 2MB page migrations.
>
> Here are the throughput numbers for different page sizes and page numbers:
> | 512 4KB pages | 1 2MB THP | 1 4KB page
> x86_64 | 0.98GB/s | 2.97GB/s | 0.06GB/s
>
> As Linux currently use single-threaded page migration, the throughput is still
> much lower than the hardware bandwidth, 2.97GB/s vs 23.4GB/s. So I parallelize
> the copy_page() part of THP migration with workqueue and achieve 2.8x throughput.
>
> Here are the throughput numbers of 2MB page migration:
> | single-threaded | 8-thread
> x86_64 2MB | 2.97GB/s | 8.58GB/s
>
Whats the impact on CPU utilization? Is there a huge impact?
Balbir Singh.
Powered by blists - more mailing lists