[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0100016397f379e8-f651e3ed-3646-4423-8cd3-9ea61666a12b-000000@email.amazonses.com>
Date: Fri, 25 May 2018 15:38:26 +0000
From: Christopher Lameter <cl@...ux.com>
To: "Huang, Ying" <ying.huang@...el.com>
cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Andi Kleen <andi.kleen@...el.com>,
Jan Kara <jack@...e.cz>, Michal Hocko <mhocko@...e.com>,
Andrea Arcangeli <aarcange@...hat.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Matthew Wilcox <mawilcox@...rosoft.com>,
Hugh Dickins <hughd@...gle.com>,
Minchan Kim <minchan@...nel.org>, Shaohua Li <shli@...com>,
Mike Kravetz <mike.kravetz@...cle.com>
Subject: Re: [PATCH -V2 -mm 0/4] mm, huge page: Copy target sub-page last
when copy huge page
On Thu, 24 May 2018, Huang, Ying wrote:
> If the cache contention is heavy when copying the huge page, and we
> copy the huge page from the begin to the end, it is possible that the
> begin of huge page is evicted from the cache after we finishing
> copying the end of the huge page. And it is possible for the
> application to access the begin of the huge page after copying the
> huge page.
Isnt there a better way to zero the remaining pages? Something that has no
cache impact like a non temporal store? So the remaining cache will not be
evicted?
https://www.felixcloutier.com/x86/MOVNTI.html
Powered by blists - more mailing lists