Re: [PATCH 0/2] Disable zone_reclaim_mode by default v2

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

 



On Tue,  8 Apr 2014 09:22:58 +0100 Mel Gorman <mgorman@xxxxxxx> wrote:

> Changelog since v1
>  o topology comment updates
> 
> When it was introduced, zone_reclaim_mode made sense as NUMA distances
> punished and workloads were generally partitioned to fit into a NUMA
> node. NUMA machines are now common but few of the workloads are NUMA-aware
> and it's routine to see major performance due to zone_reclaim_mode being
> enabled but relatively few can identify the problem.
> 
> Those that require zone_reclaim_mode are likely to be able to detect when
> it needs to be enabled and tune appropriately so lets have a sensible
> default for the bulk of users.
> 

This patchset conflicts with  

commit 70ef57e6c22c3323dce179b7d0d433c479266612
Author:     Michal Hocko <mhocko@xxxxxxx>
AuthorDate: Mon Apr 7 15:37:01 2014 -0700
Commit:     Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
CommitDate: Mon Apr 7 16:35:50 2014 -0700

    mm: exclude memoryless nodes from zone_reclaim

It was pretty simple to resolve, but please check that I didn't miss
anything.

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