Re: [PATCH 23/33] autonuma: retain page last_nid information in khugepaged

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Oct 12, 2012 at 07:37:50AM -0400, Rik van Riel wrote:
> On 10/11/2012 02:44 PM, Mel Gorman wrote:
> >On Thu, Oct 04, 2012 at 01:51:05AM +0200, Andrea Arcangeli wrote:
> >>When pages are collapsed try to keep the last_nid information from one
> >>of the original pages.
> >>
> >
> >If two pages within a THP disagree on the node, should the collapsing be
> >aborted? I would expect that the code of a remote access exceeds the
> >gain from reduced TLB overhead.
> 
> Hard to predict.  The gains from THP seem to be on the same
> order as the gains from NUMA locality, both between 5-15%
> typically.
> 

Usually yes, but in this case you know that at least 50% of those accesses
are going to be remote and as autonuma will be attempting to get hints on
the PMD level there is going to be a struggle between THP collapsing the
page and autonuma splitting it for NUMA migration. It feels to me that
the best decision in this case is to leave the page split and NUMA
hinting take place on the PTE level.

-- 
Mel Gorman
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]