Mel Gorman writes:
> On Thu, Nov 19, 2020 at 02:17:21PM +0800, Huang, Ying wrote:
>> >> Various page placement optimization based on the NUMA balancing can be
>> >> done with these flags. As the first step, in this patch, if the
>> >> memory of the application is bound to multiple nodes
On Thu, Nov 19, 2020 at 02:17:21PM +0800, Huang, Ying wrote:
> >> Various page placement optimization based on the NUMA balancing can be
> >> done with these flags. As the first step, in this patch, if the
> >> memory of the application is bound to multiple nodes (MPOL_BIND), and
> >> in the hint
Mel Gorman writes:
> On Wed, Nov 18, 2020 at 01:19:52PM +0800, Huang Ying wrote:
>> Now, AutoNUMA can only optimize the page placement among the NUMA
>
> Note that the feature is referred to as NUMA_BALANCING in the kernel
> configs as AUTONUMA as it was first presented was not merged. The
On Wed, Nov 18, 2020 at 01:19:52PM +0800, Huang Ying wrote:
> Now, AutoNUMA can only optimize the page placement among the NUMA
Note that the feature is referred to as NUMA_BALANCING in the kernel
configs as AUTONUMA as it was first presented was not merged. The sysctl
for it is
Now, AutoNUMA can only optimize the page placement among the NUMA
nodes if the default memory policy is used. Because the memory policy
specified explicitly should take precedence. But this seems too
strict in some situations. For example, on a system with 4 NUMA
nodes, if the memory of an
5 matches
Mail list logo
