On Thu, Apr 1, 2021 at 11:35 AM Dave Hansen wrote:
> This proposes extending the existing "zone_reclaim_mode" (now
> now really node_reclaim_mode) as a method to enable it.
Nit: now now -> now
> We are open to any alternative that allows end users to enable
> this mechanism or disable it it
On Thu, Apr 1, 2021 at 11:35 AM Dave Hansen wrote:
>
>
> From: Dave Hansen
>
> Some method is obviously needed to enable reclaim-based migration.
>
> Just like traditional autonuma, there will be some workloads that
> will benefit like workloads with more "static" configurations where
> hot
From: Dave Hansen
Some method is obviously needed to enable reclaim-based migration.
Just like traditional autonuma, there will be some workloads that
will benefit like workloads with more "static" configurations where
hot pages stay hot and cold pages stay cold. If pages come and go
from
On 3/8/21 4:24 PM, Yang Shi wrote:
>> Once this is enabled page demotion may move data to a NUMA node
>> that does not fall into the cpuset of the allocating process.
>> This could be construed to violate the guarantees of cpusets.
>> However, since this is an opt-in mechanism, the assumption is
On Thu, Mar 4, 2021 at 4:01 PM Dave Hansen wrote:
>
>
> From: Dave Hansen
>
> Some method is obviously needed to enable reclaim-based migration.
>
> Just like traditional autonuma, there will be some workloads that
> will benefit like workloads with more "static" configurations where
> hot pages
From: Dave Hansen
Some method is obviously needed to enable reclaim-based migration.
Just like traditional autonuma, there will be some workloads that
will benefit like workloads with more "static" configurations where
hot pages stay hot and cold pages stay cold. If pages come and go
from
6 matches
Mail list logo
