mm: page_alloc: replace mm_percpu_wq with kthreads in drain_all_pages
Subsystems (2)
Suren Baghdasaryan
reviewerRFC 1/1 mm: page_alloc: replace mm_percpu_wq with kthreads in drain_all_pages
Sending as an RFC to confirm if this is the right direction and to clarify if other tasks currently executed on mm_percpu_wq should be also moved to kthreads. The patch seems stable in testing but I want to collect more performance data before submitting a non-RFC version.
Currently drain_all_pages uses mm_percpu_wq to drain pages from pcp list during direct reclaim. The tasks on a workqueue can be delayed by other tasks in the workqueues using the same per-cpu worker pool. This results in sizable delays in drain_all_pages when cpus are highly contended.
Memory management operations designed to relieve memory pressure should not be allowed to block by other tasks, especially if the task in direct reclaim has higher priority than the blocking tasks.
Replace the usage of mm_percpu_wq with per-cpu low priority FIFO kthreads to execute draining tasks.
--- mm/page_alloc.c | 84 ++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 70 insertions(+), 14 deletions(-)
mm/page_alloc.c +70 -14
@@ -153,7 +153,8 @@ EXPORT_PER_CPU_SYMBOL(_numa_mem_);/* work_structs for global per-cpu drains */ struct pcpu_drain {struct zone *zone; -struct work_struct work; +struct kthread_work work; +struct kthread_worker *worker; };static DEFINE_MUTEX (pcpu_drain_mutex); static DEFINE_PER_CPU(struct pcpu_drain, pcpu_drain);
@@ -2209,6 +2210,58 @@ _deferred_grow_zone(struct zone *zone, unsigned int order)#endif /* CONFIG_DEFERRED_STRUCT_PAGE_INIT */ +static void drain_local_pages_func (struct kthread_work *work); + +static int alloc_drain_worker (unsigned int cpu) +{ +struct pcpu_drain *drain; + +mutex_lock (&pcpu_drain_mutex); + drain =per_cpu_ptr (&pcpu_drain, cpu); + drain->worker =kthread_create_worker_on_cpu (cpu,0 ,"pg_drain/%u" , cpu); +if (IS_ERR (drain->worker)) { + drain->worker =NULL ; +pr_err ("Failed to create pg_drain/%u\n" , cpu); + goto out; + } +/* Ensure the thread is not blocked by normal priority tasks */ +sched_set_fifo_low (drain->worker->task); +kthread_init_work (&drain->work, drain_local_pages_func); +out: +mutex_unlock (&pcpu_drain_mutex); + +return 0 ; +} + +static int free_drain_worker (unsigned int cpu) +{ +struct pcpu_drain *drain; + +mutex_lock (&pcpu_drain_mutex); + drain =per_cpu_ptr (&pcpu_drain, cpu); +kthread_cancel_work_sync (&drain->work); +kthread_destroy_worker (drain->worker); + drain->worker =NULL ; +mutex_unlock (&pcpu_drain_mutex); + +return 0 ; +} + +static void __init init_drain_workers (void ) +{ +unsigned int cpu; + +for_each_online_cpu (cpu) +alloc_drain_worker (cpu); + +if (cpuhp_setup_state_nocalls (CPUHP_AP_ONLINE_DYN , +"page_alloc/drain:online" , + alloc_drain_worker, + free_drain_worker)) { +pr_err ("page_alloc_drain: Failed to allocate a hotplug state\n" ); + } +} +void __init page_alloc_init_late (void ) {struct zone *zone;
@@ -2245,6 +2298,8 @@ void __init page_alloc_init_late(void)for_each_populated_zone (zone)set_zone_contiguous (zone); + +init_drain_workers (); }#ifdef CONFIG_CMA
@@ -3144,7 +3199,7 @@ void drain_local_pages(struct zone *zone)drain_pages (cpu); } -static void drain_local_pages_wq (struct work_struct *work) +static void drain_local_pages_func (struct kthread_work *work) {struct pcpu_drain *drain;
@@ -3175,6 +3230,7 @@ static void drain_local_pages_wq(struct work_struct *work)static void __drain_all_pages (struct zone *zone,bool force_all_cpus) {int cpu; +struct pcpu_drain *drain;/* * Allocate in the BSS so we won't require allocation in
@@ -3182,13 +3238,6 @@ static void __drain_all_pages(struct zone *zone, bool force_all_cpus)*/ static cpumask_t cpus_with_pcps; -/* -* Make sure nobody triggers this path before mm_percpu_wq is fully -* initialized. -*/ -if (WARN_ON_ONCE (!mm_percpu_wq)) -return ; -/* * Do not drain if one is already in progress unless it's specific to * a zone. Such callers are primarily CMA and memory hotplug and need
@@ -3238,14 +3287,21 @@ static void __drain_all_pages(struct zone *zone, bool force_all_cpus) }for_each_cpu (cpu, &cpus_with_pcps) { -struct pcpu_drain *drain =per_cpu_ptr (&pcpu_drain, cpu); + drain =per_cpu_ptr (&pcpu_drain, cpu); drain->zone = zone; -INIT_WORK (&drain->work, drain_local_pages_wq); -queue_work_on (cpu, mm_percpu_wq, &drain->work); +if (likely (drain->worker)) +kthread_queue_work (drain->worker, &drain->work); + } +/* Wait for kthreads to finish or drain itself */ +for_each_cpu (cpu, &cpus_with_pcps) { + drain =per_cpu_ptr (&pcpu_drain, cpu); + +if (likely (drain->worker)) +kthread_flush_work (&drain->work); +else +drain_local_pages_func (&drain->work); } -for_each_cpu (cpu, &cpus_with_pcps) -flush_work (&per_cpu_ptr (&pcpu_drain, cpu)->work);mutex_unlock (&pcpu_drain_mutex); }
Signature · 1 line
2.35.1.574.g5d30c73bfb-goog
Quoted 17 lines · Suren Baghdasaryan
Sending as an RFC to confirm if this is the right direction and to clarify if other tasks currently executed on
mm_percpu_wqshould be also moved to kthreads. The patch seems stable in testing but I want to collect more performance data before submitting a non-RFC version.Currently
drain_all_pagesusesmm_percpu_wqto drain pages from pcp list during direct reclaim. The tasks on a workqueue can be delayed by other tasks in the workqueues using the same per-cpu worker pool. This results in sizable delays indrain_all_pageswhen cpus are highly contended.
Memory management operations designed to relieve memory pressure should not be allowed to block by other tasks, especially if the task in direct reclaim has higher priority than the blocking tasks.
Replace the usage ofmm_percpu_wqwith per-cpu low priority FIFO kthreads to execute draining tasks.
Quoted 2 lines
Suggested-by Petr Mladek <[email protected]>Signed-off-by Suren Baghdasaryan <[email protected]>
The patch looks good to me. See few comments below about things where I was in doubts. But I do not see any real problem with this approach.
Quoted 32 lines
--- mm/page_alloc.c | 84 ++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 70 insertions(+), 14 deletions(-)mm/page_alloc.c +20
-0@@ -2209,6 +2210,58 @@ _deferred_grow_zone(struct zone *zone, unsigned int order)#endif /* CONFIG_DEFERRED_STRUCT_PAGE_INIT */ +static void drain_local_pages_func (struct kthread_work *work); + +static int alloc_drain_worker (unsigned int cpu) +{ +struct pcpu_drain *drain; + +mutex_lock (&pcpu_drain_mutex); + drain =per_cpu_ptr (&pcpu_drain, cpu); + drain->worker =kthread_create_worker_on_cpu (cpu,0 ,"pg_drain/%u" , cpu); +if (IS_ERR (drain->worker)) { + drain->worker =NULL ; +pr_err ("Failed to create pg_drain/%u\n" , cpu); + goto out; + } +/* Ensure the thread is not blocked by normal priority tasks */ +sched_set_fifo_low (drain->worker->task); +kthread_init_work (&drain->work, drain_local_pages_func); +out: +mutex_unlock (&pcpu_drain_mutex); +
mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2242
Quoted 10 lines
mm/page_alloc.c +10
-0+return 0 ; +} + +static int free_drain_worker (unsigned int cpu) +{ +struct pcpu_drain *drain; + +mutex_lock (&pcpu_drain_mutex); + drain =per_cpu_ptr (&pcpu_drain, cpu); +kthread_cancel_work_sync (&drain->work);
I do see not how CPU down was handled in the original code.
Note that workqueues call unbind_workers() when a CPU is going down. The pending work items might be proceed on another CPU. From this POV, the new code looks more safe.
mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2255
Quoted 13 lines
mm/page_alloc.c +13
-0+kthread_destroy_worker (drain->worker); + drain->worker =NULL ; +mutex_unlock (&pcpu_drain_mutex); + +return 0 ; +} + +static void __init init_drain_workers (void ) +{ +unsigned int cpu; + +for_each_online_cpu (cpu) +alloc_drain_worker (cpu);
I though whether this need to be called under cpus_read_lock(); And I think that the code should be safe as it is. There is this call chain:
+ kernel_init_freeable()
+ page_alloc_init_late()
+ init_drain_workers()
It is called after smp_init() but before the init process is executed. I guess that nobody could trigger CPU hotplug at this state. So there there is no need to synchronize against it.
mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2261
Quoted 6 lines
mm/page_alloc.c +6
-0+ +if (cpuhp_setup_state_nocalls (CPUHP_AP_ONLINE_DYN , +"page_alloc/drain:online" , + alloc_drain_worker, + free_drain_worker)) { +pr_err ("page_alloc_drain: Failed to allocate a hotplug state\n" );
I am not sure if there are any special requirements about the ordering vs. other CPU hotplug operations.
Just note that the per-CPU workqueues are started/stopped via CPUHP_AP_WORKQUEUE_ONLINE. They are available slightly earlier before CPUHP_AP_ONLINE_DYN when the CPU is being enabled.
mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2267
Quoted 6 lines
mm/page_alloc.c +3
-0+ } +} +void __init page_alloc_init_late (void ) {struct zone *zone;
Best Regards,
Petr
Suren Baghdasaryan
reviewerQuoted 19 lines · Petr Mladek
Quoted 17 lines · Suren Baghdasaryan
Sending as an RFC to confirm if this is the right direction and to clarify if other tasks currently executed on
mm_percpu_wqshould be also moved to kthreads. The patch seems stable in testing but I want to collect more performance data before submitting a non-RFC version.Currently
drain_all_pagesusesmm_percpu_wqto drain pages from pcp list during direct reclaim. The tasks on a workqueue can be delayed by other tasks in the workqueues using the same per-cpu worker pool. This results in sizable delays indrain_all_pageswhen cpus are highly contended.
Memory management operations designed to relieve memory pressure should not be allowed to block by other tasks, especially if the task in direct reclaim has higher priority than the blocking tasks.
Replace the usage ofmm_percpu_wqwith per-cpu low priority FIFO kthreads to execute draining tasks.
Quoted 6 lines
Quoted 2 lines
Suggested-by Petr Mladek <[email protected]>Signed-off-by Suren Baghdasaryan <[email protected]>The patch looks good to me. See few comments below about things where I was in doubts. But I do not see any real problem with this approach.
Thanks for the review, Petr. One question inline.
Other than that I would like to check if:
1. Using low priority FIFO for these kthreads is warranted. From
https://lore.kernel.org/all/CAEe=Sxmow-jx60cDjFMY7qi7+KVc+BT++BTdwC5+G9E=1soMmQ@mail.gmail.com/#t
my understanding was that we want this work to be done by RT kthread_worker but maybe that's not appropriate here?
2. Do we want to move any other work done on mm_percpu_wq (vmstat_work, lru_add_drain_all) to these kthreads?
If what I have currently is ok, I'll post the first version. Thanks,
Suren.
Quoted 69 lines
Quoted 33 lines
--- mm/page_alloc.c | 84 ++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 70 insertions(+), 14 deletions(-)mm/page_alloc.c +20
-0@@ -2209,6 +2210,58 @@ _deferred_grow_zone(struct zone *zone, unsigned int order)#endif /* CONFIG_DEFERRED_STRUCT_PAGE_INIT */ +static void drain_local_pages_func (struct kthread_work *work); + +static int alloc_drain_worker (unsigned int cpu) +{ +struct pcpu_drain *drain; + +mutex_lock (&pcpu_drain_mutex); + drain =per_cpu_ptr (&pcpu_drain, cpu); + drain->worker =kthread_create_worker_on_cpu (cpu,0 ,"pg_drain/%u" , cpu); +if (IS_ERR (drain->worker)) { + drain->worker =NULL ; +pr_err ("Failed to create pg_drain/%u\n" , cpu); + goto out; + } +/* Ensure the thread is not blocked by normal priority tasks */ +sched_set_fifo_low (drain->worker->task); +kthread_init_work (&drain->work, drain_local_pages_func); +out: +mutex_unlock (&pcpu_drain_mutex); +mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2242
Quoted 10 lines
mm/page_alloc.c +10
-0+return 0 ; +} + +static int free_drain_worker (unsigned int cpu) +{ +struct pcpu_drain *drain; + +mutex_lock (&pcpu_drain_mutex); + drain =per_cpu_ptr (&pcpu_drain, cpu); +kthread_cancel_work_sync (&drain->work);I do see not how CPU down was handled in the original code.
Note that workqueues call
unbind_workers()when a CPU is going down. The pending work items might be proceed on another CPU. From this POV, the new code looks more safe.mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2255
Quoted 13 lines
mm/page_alloc.c +13
-0+kthread_destroy_worker (drain->worker); + drain->worker =NULL ; +mutex_unlock (&pcpu_drain_mutex); + +return 0 ; +} + +static void __init init_drain_workers (void ) +{ +unsigned int cpu; + +for_each_online_cpu (cpu) +alloc_drain_worker (cpu);I though whether this need to be called under
cpus_read_lock(); And I think that the code should be safe as it is. There is this call chain:
Quoted 8 lines
+
kernel_init_freeable()
+page_alloc_init_late()
+init_drain_workers()It is called after
smp_init()but before the init process is executed. I guess that nobody could trigger CPU hotplug at this state. So there there is no need to synchronize against it.
Should I add a comment here to describe why we don't need cpus_read_lock here (due to init process not being active at this time)?
Quoted 25 lines
mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2261
Quoted 7 lines
mm/page_alloc.c +6
-0+ +if (cpuhp_setup_state_nocalls (CPUHP_AP_ONLINE_DYN , +"page_alloc/drain:online" , + alloc_drain_worker, + free_drain_worker)) { +pr_err ("page_alloc_drain: Failed to allocate a hotplug state\n" );I am not sure if there are any special requirements about the ordering vs. other CPU hotplug operations.
Just note that the per-CPU workqueues are started/stopped via
CPUHP_AP_WORKQUEUE_ONLINE. They are available slightly earlier beforeCPUHP_AP_ONLINE_DYNwhen the CPU is being enabled.mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2267
Quoted 6 lines
mm/page_alloc.c +3
-0+ } +} +void __init page_alloc_init_late (void ) {struct zone *zone;Best Regards,
Petr
Quoted 20 lines · Suren Baghdasaryan
Quoted 19 lines · Petr Mladek
Quoted 17 lines · Suren Baghdasaryan
Sending as an RFC to confirm if this is the right direction and to clarify if other tasks currently executed on
mm_percpu_wqshould be also moved to kthreads. The patch seems stable in testing but I want to collect more performance data before submitting a non-RFC version.Currently
drain_all_pagesusesmm_percpu_wqto drain pages from pcp list during direct reclaim. The tasks on a workqueue can be delayed by other tasks in the workqueues using the same per-cpu worker pool. This results in sizable delays indrain_all_pageswhen cpus are highly contended.
Memory management operations designed to relieve memory pressure should not be allowed to block by other tasks, especially if the task in direct reclaim has higher priority than the blocking tasks.
Replace the usage ofmm_percpu_wqwith per-cpu low priority FIFO kthreads to execute draining tasks.
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
Suggested-by Petr Mladek <[email protected]>Signed-off-by Suren Baghdasaryan <[email protected]>The patch looks good to me. See few comments below about things where I was in doubts. But I do not see any real problem with this approach.
Thanks for the review, Petr. One question inline.
Answering just this question.
Quoted 19 lines
Quoted 19 lines
mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2255
Quoted 10 lines
mm/page_alloc.c +6
-0+static void __init init_drain_workers (void ) +{ +unsigned int cpu; + +for_each_online_cpu (cpu) +alloc_drain_worker (cpu);I though whether this need to be called under
cpus_read_lock(); And I think that the code should be safe as it is. There is this call chain:+
kernel_init_freeable()
+page_alloc_init_late()
+init_drain_workers()
Quoted 8 lines
Quoted 4 lines
It is called after
smp_init()but before the init process is executed. I guess that nobody could trigger CPU hotplug at this state. So there there is no need to synchronize against it.Should I add a comment here to describe why we don't need
cpus_read_lockhere (due to init process not being active at this time)?
I would add the comment. That said, I hope that I am right and lock is not really needed ;-)
Best Regards,
Petr
Quoted 9 lines · On Thu, 24 Feb 2022 17:28:19 -0800 Suren Baghdasaryan wrote:
Sending as an RFC to confirm if this is the right direction and to clarify if other tasks currently executed on
mm_percpu_wqshould be also moved to kthreads. The patch seems stable in testing but I want to collect more performance data before submitting a non-RFC version.Currently
drain_all_pagesusesmm_percpu_wqto drain pages from pcp list during direct reclaim. The tasks on a workqueue can be delayed by other tasks in the workqueues using the same per-cpu worker pool.
The pending works may be freeing a couple of slabs/pages each. Who knows?
Quoted 5 lines
This results in sizable delays in
drain_all_pageswhen cpus are highly contended.
Memory management operations designed to relieve memory pressure should not be allowed to block by other tasks, especially if the task in direct reclaim has higher priority than the blocking tasks.
Wonder why priority is the right cure to tight memory - otherwise it was not a problem given a direct reclaimer of higher priority.
Off topic question - why is it making sense from begining for a task of lower priority to peel pages off from another of higher priority if priority is considered in direct reclaim?
Quoted 24 lines
Replace the usage of
mm_percpu_wqwith per-cpu low priority FIFO kthreads to execute draining tasks.Suggested-by Petr Mladek <[email protected]>Signed-off-by Suren Baghdasaryan <[email protected]>--- mm/page_alloc.c | 84 ++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 70 insertions(+), 14 deletions(-)mm/page_alloc.c +2
-1@@ -153,7 +153,8 @@ EXPORT_PER_CPU_SYMBOL(_numa_mem_);/* work_structs for global per-cpu drains */ struct pcpu_drain {struct zone *zone; -struct work_struct work; +struct kthread_work work; +struct kthread_worker *worker; };static DEFINE_MUTEX (pcpu_drain_mutex); static DEFINE_PER_CPU(struct pcpu_drain, pcpu_drain);
mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2219
Quoted 10 lines
mm/page_alloc.c +7
-0@@ -2209,6 +2210,58 @@ _deferred_grow_zone(struct zone *zone, unsigned int order)#endif /* CONFIG_DEFERRED_STRUCT_PAGE_INIT */ +static void drain_local_pages_func (struct kthread_work *work); + +static int alloc_drain_worker (unsigned int cpu) +{ +struct pcpu_drain *drain; + +mutex_lock (&pcpu_drain_mutex);
Nit, see below.
Quoted 5 lines
mm/page_alloc.c +5
-0+ drain =per_cpu_ptr (&pcpu_drain, cpu); + drain->worker =kthread_create_worker_on_cpu (cpu,0 ,"pg_drain/%u" , cpu); +if (IS_ERR (drain->worker)) { + drain->worker =NULL ; +pr_err ("Failed to create pg_drain/%u\n" , cpu);
mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2234
Quoted 10 lines
mm/page_alloc.c +10
-0+ goto out; + } +/* Ensure the thread is not blocked by normal priority tasks */ +sched_set_fifo_low (drain->worker->task); +kthread_init_work (&drain->work, drain_local_pages_func); +out: +mutex_unlock (&pcpu_drain_mutex); + +return 0 ; +}
alloc_drain_worker(unsigned int cpu)
mutex_lock(&pcpu_drain_mutex);
drain->worker = kthread_create_worker_on_cpu(cpu, 0, "pg_drain/%u", cpu);
__kthread_create_worker(cpu, flags, namefmt, args);
kzalloc(sizeof(*worker), GFP_KERNEL);
kmalloc
slab_alloc
new_slab
alloc_pages
__alloc_pages_slowpath
__alloc_pages_direct_reclaim
drain_all_pages(NULL);
__drain_all_pages(zone, false);
if (unlikely(!mutex_trylock(&pcpu_drain_mutex))) {
if (!zone)
return;
mutex_lock(&pcpu_drain_mutex);
}Either deadlock or no page drained wrt pcpu_drain_mutex if nothing missed.
Quoted 104 lines
mm/page_alloc.c +46
-13+ +static int free_drain_worker (unsigned int cpu) +{ +struct pcpu_drain *drain; + +mutex_lock (&pcpu_drain_mutex); + drain =per_cpu_ptr (&pcpu_drain, cpu); +kthread_cancel_work_sync (&drain->work); +kthread_destroy_worker (drain->worker); + drain->worker =NULL ; +mutex_unlock (&pcpu_drain_mutex); + +return 0 ; +} + +static void __init init_drain_workers (void ) +{ +unsigned int cpu; + +for_each_online_cpu (cpu) +alloc_drain_worker (cpu); + +if (cpuhp_setup_state_nocalls (CPUHP_AP_ONLINE_DYN , +"page_alloc/drain:online" , + alloc_drain_worker, + free_drain_worker)) { +pr_err ("page_alloc_drain: Failed to allocate a hotplug state\n" ); + } +} +void __init page_alloc_init_late (void ) {struct zone *zone;@@ -2245,6 +2298,8 @@ void __init page_alloc_init_late(void)for_each_populated_zone (zone)set_zone_contiguous (zone); + +init_drain_workers (); }#ifdef CONFIG_CMA @@ -3144,7 +3199,7 @@ void drain_local_pages(struct zone *zone)drain_pages (cpu); } -static void drain_local_pages_wq (struct work_struct *work) +static void drain_local_pages_func (struct kthread_work *work) {struct pcpu_drain *drain;@@ -3175,6 +3230,7 @@ static void drain_local_pages_wq(struct work_struct *work)static void __drain_all_pages (struct zone *zone,bool force_all_cpus) {int cpu; +struct pcpu_drain *drain;/* * Allocate in the BSS so we won't require allocation in @@ -3182,13 +3238,6 @@ static void __drain_all_pages(struct zone *zone, bool force_all_cpus)*/ static cpumask_t cpus_with_pcps; -/* -* Make sure nobody triggers this path before mm_percpu_wq is fully -* initialized. -*/ -if (WARN_ON_ONCE (!mm_percpu_wq)) -return ; -/* * Do not drain if one is already in progress unless it's specific to * a zone. Such callers are primarily CMA and memory hotplug and need @@ -3238,14 +3287,21 @@ static void __drain_all_pages(struct zone *zone, bool force_all_cpus) }for_each_cpu (cpu, &cpus_with_pcps) { -struct pcpu_drain *drain =per_cpu_ptr (&pcpu_drain, cpu); + drain =per_cpu_ptr (&pcpu_drain, cpu); drain->zone = zone; -INIT_WORK (&drain->work, drain_local_pages_wq); -queue_work_on (cpu, mm_percpu_wq, &drain->work); +if (likely (drain->worker)) +kthread_queue_work (drain->worker, &drain->work); + } +/* Wait for kthreads to finish or drain itself */ +for_each_cpu (cpu, &cpus_with_pcps) { + drain =per_cpu_ptr (&pcpu_drain, cpu); + +if (likely (drain->worker)) +kthread_flush_work (&drain->work); +else +drain_local_pages_func (&drain->work); } -for_each_cpu (cpu, &cpus_with_pcps) -flush_work (&per_cpu_ptr (&pcpu_drain, cpu)->work);mutex_unlock (&pcpu_drain_mutex); }Signature · 1 line
2.35.1.574.g5d30c73bfb-goog
Suren Baghdasaryan
reviewerQuoted 8 lines · Hillf Danton
Quoted 6 lines · On Thu, 24 Feb 2022 17:28:19 -0800 Suren Baghdasaryan wrote:
Sending as an RFC to confirm if this is the right direction and to clarify if other tasks currently executed on
mm_percpu_wqshould be also moved to kthreads. The patch seems stable in testing but I want to collect more performance data before submitting a non-RFC version.
Quoted 5 lines
Quoted 3 lines
Currently
drain_all_pagesusesmm_percpu_wqto drain pages from pcp list during direct reclaim. The tasks on a workqueue can be delayed by other tasks in the workqueues using the same per-cpu worker pool.The pending works may be freeing a couple of slabs/pages each. Who knows?
If we are talking about work specifically scheduled on mm_percpu_wq then apart from drain_all_pages, mm_percpu_wq is used to execute vmstat_update and lru_add_drain_cpu for drainig pagevecs. If OTOH what you mean is that the work might be blocked by say kswapd, which is freeing memory, then sure, who knows...
Quoted 7 lines
Quoted 6 lines
This results in sizable delays in
drain_all_pageswhen cpus are highly contended.
Memory management operations designed to relieve memory pressure should not be allowed to block by other tasks, especially if the task in direct reclaim has higher priority than the blocking tasks.
Quoted 6 lines
Wonder why priority is the right cure to tight memory - otherwise it was not a problem given a direct reclaimer of higher priority.
Off topic question - why is it making sense from begining for a task of lower priority to peel pages off from another of higher priority if priority is considered in direct reclaim?
The way I understood your question is that you are asking why we have to use workqueues of potentially lower priority to drain pages for a potentially higher priority process in direct reclaim (which is blocked waiting for workqueues to complete draining)?
If so, IIUC this mechanism was introduced in
https://lore.kernel.org/all/[email protected]
to avoid draining from IPI context (CC'ing Mel Gorman to correct me if I'm wrong).
I think the issue here is that in the process we are losing information about the priority of the process in direct reclaim, which might lead to priority inversion.
I'm not sure at all if this is the right solution here, hence sending this as RFC to gather more feedback.
The discussion that lead to this patch starts here:
https://lore.kernel.org/all/[email protected] (CC'ing people who were involved in that discussion)
Quoted 73 lines
Quoted 25 lines
Replace the usage of
mm_percpu_wqwith per-cpu low priority FIFO kthreads to execute draining tasks.Suggested-by Petr Mladek <[email protected]>Signed-off-by Suren Baghdasaryan <[email protected]>--- mm/page_alloc.c | 84 ++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 70 insertions(+), 14 deletions(-)mm/page_alloc.c +2
-1@@ -153,7 +153,8 @@ EXPORT_PER_CPU_SYMBOL(_numa_mem_);/* work_structs for global per-cpu drains */ struct pcpu_drain {struct zone *zone; -struct work_struct work; +struct kthread_work work; +struct kthread_worker *worker; };static DEFINE_MUTEX (pcpu_drain_mutex); static DEFINE_PER_CPU(struct pcpu_drain, pcpu_drain);mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2219
Quoted 10 lines
mm/page_alloc.c +7
-0@@ -2209,6 +2210,58 @@ _deferred_grow_zone(struct zone *zone, unsigned int order)#endif /* CONFIG_DEFERRED_STRUCT_PAGE_INIT */ +static void drain_local_pages_func (struct kthread_work *work); + +static int alloc_drain_worker (unsigned int cpu) +{ +struct pcpu_drain *drain; + +mutex_lock (&pcpu_drain_mutex);Nit, see below.
Quoted 5 lines
mm/page_alloc.c +5
-0+ drain =per_cpu_ptr (&pcpu_drain, cpu); + drain->worker =kthread_create_worker_on_cpu (cpu,0 ,"pg_drain/%u" , cpu); +if (IS_ERR (drain->worker)) { + drain->worker =NULL ; +pr_err ("Failed to create pg_drain/%u\n" , cpu);mm/page_alloc.c _deferred_grow_zone(struct zone *zone, unsigned int order) · line 2234
Quoted 10 lines
mm/page_alloc.c +10
-0+ goto out; + } +/* Ensure the thread is not blocked by normal priority tasks */ +sched_set_fifo_low (drain->worker->task); +kthread_init_work (&drain->work, drain_local_pages_func); +out: +mutex_unlock (&pcpu_drain_mutex); + +return 0 ; +}
alloc_drain_worker(unsigned int cpu)
mutex_lock(&pcpu_drain_mutex);drain->worker = kthread_create_worker_on_cpu(cpu, 0, "pg_drain/%u", cpu); __kthread_create_worker(cpu, flags, namefmt, args); kzalloc(sizeof(*worker), GFP_KERNEL); kmalloc slab_alloc new_slab alloc_pages __alloc_pages_slowpath __alloc_pages_direct_reclaim drain_all_pages(NULL); __drain_all_pages(zone, false); if (unlikely(!mutex_trylock(&pcpu_drain_mutex))) { if (!zone) return; mutex_lock(&pcpu_drain_mutex); }
Quoted 1 line
Either deadlock or no page drained wrt
pcpu_drain_mutexif nothing missed.
Thanks for noticing it! I think this can be easily fixed by calling kthread_create_worker_on_cpu outside of the pcpu_drain_mutex protection and then assigning the result to drain->worker after taking pcpu_drain_mutex.
Thanks,
Suren.
Quoted 106 lines
Quoted 105 lines
mm/page_alloc.c +46
-14+ +static int free_drain_worker (unsigned int cpu) +{ +struct pcpu_drain *drain; + +mutex_lock (&pcpu_drain_mutex); + drain =per_cpu_ptr (&pcpu_drain, cpu); +kthread_cancel_work_sync (&drain->work); +kthread_destroy_worker (drain->worker); + drain->worker =NULL ; +mutex_unlock (&pcpu_drain_mutex); + +return 0 ; +} + +static void __init init_drain_workers (void ) +{ +unsigned int cpu; + +for_each_online_cpu (cpu) +alloc_drain_worker (cpu); + +if (cpuhp_setup_state_nocalls (CPUHP_AP_ONLINE_DYN , +"page_alloc/drain:online" , + alloc_drain_worker, + free_drain_worker)) { +pr_err ("page_alloc_drain: Failed to allocate a hotplug state\n" ); + } +} +void __init page_alloc_init_late (void ) {struct zone *zone;@@ -2245,6 +2298,8 @@ void __init page_alloc_init_late(void)for_each_populated_zone (zone)set_zone_contiguous (zone); + +init_drain_workers (); }#ifdef CONFIG_CMA @@ -3144,7 +3199,7 @@ void drain_local_pages(struct zone *zone)drain_pages (cpu); } -static void drain_local_pages_wq (struct work_struct *work) +static void drain_local_pages_func (struct kthread_work *work) {struct pcpu_drain *drain;@@ -3175,6 +3230,7 @@ static void drain_local_pages_wq(struct work_struct *work)static void __drain_all_pages (struct zone *zone,bool force_all_cpus) {int cpu; +struct pcpu_drain *drain;/* * Allocate in the BSS so we won't require allocation in @@ -3182,13 +3238,6 @@ static void __drain_all_pages(struct zone *zone, bool force_all_cpus)*/ static cpumask_t cpus_with_pcps; -/* -* Make sure nobody triggers this path before mm_percpu_wq is fully -* initialized. -*/ -if (WARN_ON_ONCE (!mm_percpu_wq)) -return ; -/* * Do not drain if one is already in progress unless it's specific to * a zone. Such callers are primarily CMA and memory hotplug and need @@ -3238,14 +3287,21 @@ static void __drain_all_pages(struct zone *zone, bool force_all_cpus) }for_each_cpu (cpu, &cpus_with_pcps) { -struct pcpu_drain *drain =per_cpu_ptr (&pcpu_drain, cpu); + drain =per_cpu_ptr (&pcpu_drain, cpu); drain->zone = zone; -INIT_WORK (&drain->work, drain_local_pages_wq); -queue_work_on (cpu, mm_percpu_wq, &drain->work); +if (likely (drain->worker)) +kthread_queue_work (drain->worker, &drain->work); + } +/* Wait for kthreads to finish or drain itself */ +for_each_cpu (cpu, &cpus_with_pcps) { + drain =per_cpu_ptr (&pcpu_drain, cpu); + +if (likely (drain->worker)) +kthread_flush_work (&drain->work); +else +drain_local_pages_func (&drain->work); } -for_each_cpu (cpu, &cpus_with_pcps) -flush_work (&per_cpu_ptr (&pcpu_drain, cpu)->work);mutex_unlock (&pcpu_drain_mutex); } --2.35.1.574.g5d30c73bfb-goog
Quoted 13 lines · Suren Baghdasaryan
Quoted 12 lines · Hillf Danton
Quoted 9 lines · On Thu, 24 Feb 2022 17:28:19 -0800 Suren Baghdasaryan wrote:
Sending as an RFC to confirm if this is the right direction and to clarify if other tasks currently executed on
mm_percpu_wqshould be also moved to kthreads. The patch seems stable in testing but I want to collect more performance data before submitting a non-RFC version.Currently
drain_all_pagesusesmm_percpu_wqto drain pages from pcp list during direct reclaim. The tasks on a workqueue can be delayed by other tasks in the workqueues using the same per-cpu worker pool.
Quoted 7 lines
Quoted 1 line
The pending works may be freeing a couple of slabs/pages each. Who knows?
If we are talking about work specifically scheduled on
mm_percpu_wqthen apart fromdrain_all_pages,mm_percpu_wqis used to executevmstat_updateandlru_add_drain_cpufor drainig pagevecs. If OTOH what you mean is that the work might be blocked by say kswapd, which is freeing memory, then sure, who knows...
Note that the same worker pool is used by many workqueues. And work items in per-cpu workqueues are serialized on a single worker. Another worker is used only when a work goes into a sleeping wait.
I want to say that "drain_all_pages" are not blocked only by other works using "mm_percpu_wq" but also by works from many other workqueues, including "system_wq".
These works might do anything, including memory allocation, freeing.
Quoted 14 lines
Quoted 7 lines
Quoted 6 lines
This results in sizable delays in
drain_all_pageswhen cpus are highly contended.
Memory management operations designed to relieve memory pressure should not be allowed to block by other tasks, especially if the task in direct reclaim has higher priority than the blocking tasks.Quoted 6 lines
Wonder why priority is the right cure to tight memory - otherwise it was not a problem given a direct reclaimer of higher priority.
Off topic question - why is it making sense from begining for a task of lower priority to peel pages off from another of higher priority if priority is considered in direct reclaim?
Quoted 11 lines
The way I understood your question is that you are asking why we have to use workqueues of potentially lower priority to drain pages for a potentially higher priority process in direct reclaim (which is blocked waiting for workqueues to complete draining)?
If so, IIUC this mechanism was introduced in
https://lore.kernel.org/all/[email protected]
to avoid draining from IPI context (CC'ing Mel Gorman to correct me if I'm wrong).
I think the issue here is that in the process we are losing information about the priority of the process in direct reclaim, which might lead to priority inversion.
Note that priority of workqueue workers is static. It is defined by the workqueue parameters.
kthread_worker API allows to create custom kthreads. The user could modify the priority as needed. It allows to prevent priority inversion. It can hardly be achieved by workques where the workers are heavily shared by unrelated tasks.
Best Regards,
Petr
Suren Baghdasaryan
reviewerQuoted 27 lines · Petr Mladek
Quoted 13 lines · Suren Baghdasaryan
Quoted 12 lines · Hillf Danton
Quoted 9 lines · On Thu, 24 Feb 2022 17:28:19 -0800 Suren Baghdasaryan wrote:
Sending as an RFC to confirm if this is the right direction and to clarify if other tasks currently executed on
mm_percpu_wqshould be also moved to kthreads. The patch seems stable in testing but I want to collect more performance data before submitting a non-RFC version.Currently
drain_all_pagesusesmm_percpu_wqto drain pages from pcp list during direct reclaim. The tasks on a workqueue can be delayed by other tasks in the workqueues using the same per-cpu worker pool.Quoted 7 lines
Quoted 1 line
The pending works may be freeing a couple of slabs/pages each. Who knows?
If we are talking about work specifically scheduled on
mm_percpu_wqthen apart fromdrain_all_pages,mm_percpu_wqis used to executevmstat_updateandlru_add_drain_cpufor drainig pagevecs. If OTOH what you mean is that the work might be blocked by say kswapd, which is freeing memory, then sure, who knows...Note that the same worker pool is used by many workqueues. And work items in per-cpu workqueues are serialized on a single worker. Another worker is used only when a work goes into a sleeping wait.
Quoted 5 lines
I want to say that "
drain_all_pages" are not blocked only by other works using "mm_percpu_wq" but also by works from many other workqueues, including "system_wq".These works might do anything, including memory allocation, freeing.
Ah, I didn't know this (I think you mentioned it in one of your previous replies but I missed it). Thank you for clarifying!
Quoted 27 lines
Quoted 15 lines
Quoted 8 lines
Quoted 7 lines
This results in sizable delays in
drain_all_pageswhen cpus are highly contended.
Memory management operations designed to relieve memory pressure should not be allowed to block by other tasks, especially if the task in direct reclaim has higher priority than the blocking tasks.Quoted 6 lines
Wonder why priority is the right cure to tight memory - otherwise it was not a problem given a direct reclaimer of higher priority.
Off topic question - why is it making sense from begining for a task of lower priority to peel pages off from another of higher priority if priority is considered in direct reclaim?
Quoted 11 lines
The way I understood your question is that you are asking why we have to use workqueues of potentially lower priority to drain pages for a potentially higher priority process in direct reclaim (which is blocked waiting for workqueues to complete draining)?
If so, IIUC this mechanism was introduced in
https://lore.kernel.org/all/[email protected]
to avoid draining from IPI context (CC'ing Mel Gorman to correct me if I'm wrong).
I think the issue here is that in the process we are losing information about the priority of the process in direct reclaim, which might lead to priority inversion.
Quoted 7 lines
Note that priority of workqueue workers is static. It is defined by the workqueue parameters.
kthread_workerAPI allows to create custom kthreads. The user could modify the priority as needed. It allows to prevent priority inversion. It can hardly be achieved by workques where the workers are heavily shared by unrelated tasks.
Yes but I suspect we would not want to dynamically change the priority of the kthreads performing drain_all_pages? I guess we could adjust it based on the highest priority among the tasks waiting for drain_all_pages and that would eliminate priority inversion. However I'm not sure about the possible overhead associated with such dynamic priority adjustments.
My RFC sets up the kthreads to be low priority FIFO threads. It's a simplification and I'm not sure that is the right approach here...
Quoted 3 lines
Best Regards,
Petr
Michal Hocko
reviewerQuoted 11 lines · Suren Baghdasaryan
Sending as an RFC to confirm if this is the right direction and to clarify if other tasks currently executed on
mm_percpu_wqshould be also moved to kthreads. The patch seems stable in testing but I want to collect more performance data before submitting a non-RFC version.Currently
drain_all_pagesusesmm_percpu_wqto drain pages from pcp list during direct reclaim. The tasks on a workqueue can be delayed by other tasks in the workqueues using the same per-cpu worker pool. This results in sizable delays indrain_all_pageswhen cpus are highly contended.
This is not about cpus being highly contended. It is about too much work on the WQ context.
Quoted 3 lines
Memory management operations designed to relieve memory pressure should not be allowed to block by other tasks, especially if the task in direct reclaim has higher priority than the blocking tasks.
Agreed here.
Quoted 2 lines
Replace the usage of
mm_percpu_wqwith per-cpu low priority FIFO kthreads to execute draining tasks.
This looks like a natural thing to do when WQ context is not suitable but I am not sure the additional resources is really justified. Large machines with a lot of cpus would create a lot of kernel threads. Can we do better than that?
Would it be possible to have fewer workers (e.g. 1 or one per numa node) and it would perform the work on a dedicated cpu by changing its affinity? Or would that introduce an unacceptable overhead?
Or would it be possible to update the existing WQ code to use rescuer well before the WQ is completely clogged?
Signature · 2 lines
Michal Hocko SUSE Labs
Suren Baghdasaryan
reviewerQuoted 8 lines · Michal Hocko' via kernel-team
Quoted 6 lines · Suren Baghdasaryan
Sending as an RFC to confirm if this is the right direction and to clarify if other tasks currently executed on
mm_percpu_wqshould be also moved to kthreads. The patch seems stable in testing but I want to collect more performance data before submitting a non-RFC version.
Quoted 8 lines
Quoted 5 lines
Currently
drain_all_pagesusesmm_percpu_wqto drain pages from pcp list during direct reclaim. The tasks on a workqueue can be delayed by other tasks in the workqueues using the same per-cpu worker pool. This results in sizable delays indrain_all_pageswhen cpus are highly contended.This is not about cpus being highly contended. It is about too much work on the WQ context.
Ack.
Quoted 10 lines
Quoted 4 lines
Memory management operations designed to relieve memory pressure should not be allowed to block by other tasks, especially if the task in direct reclaim has higher priority than the blocking tasks.
Agreed here.
Quoted 2 lines
Replace the usage of
mm_percpu_wqwith per-cpu low priority FIFO kthreads to execute draining tasks.
Quoted 8 lines
This looks like a natural thing to do when WQ context is not suitable but I am not sure the additional resources is really justified. Large machines with a lot of cpus would create a lot of kernel threads. Can we do better than that?
Would it be possible to have fewer workers (e.g. 1 or one per numa node) and it would perform the work on a dedicated cpu by changing its affinity? Or would that introduce an unacceptable overhead?
Not sure but I can try implementing per-node kthreads and measure the performance of the reclaim path, comparing with the current and with per-cpu approach.
Quoted 10 lines
Or would it be possible to update the existing WQ code to use rescuer well before the WQ is completely clogged?
--
Michal Hocko
SUSE Labs--
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
Suren Baghdasaryan
reviewerQuoted 37 lines · Suren Baghdasaryan
Quoted 8 lines · Michal Hocko' via kernel-team
Quoted 6 lines · Suren Baghdasaryan
Sending as an RFC to confirm if this is the right direction and to clarify if other tasks currently executed on
mm_percpu_wqshould be also moved to kthreads. The patch seems stable in testing but I want to collect more performance data before submitting a non-RFC version.Quoted 8 lines
Quoted 5 lines
Currently
drain_all_pagesusesmm_percpu_wqto drain pages from pcp list during direct reclaim. The tasks on a workqueue can be delayed by other tasks in the workqueues using the same per-cpu worker pool. This results in sizable delays indrain_all_pageswhen cpus are highly contended.This is not about cpus being highly contended. It is about too much work on the WQ context.
Ack.
Quoted 15 lines
Quoted 4 lines
Memory management operations designed to relieve memory pressure should not be allowed to block by other tasks, especially if the task in direct reclaim has higher priority than the blocking tasks.
Agreed here.
Quoted 2 lines
Replace the usage of
mm_percpu_wqwith per-cpu low priority FIFO kthreads to execute draining tasks.This looks like a natural thing to do when WQ context is not suitable but I am not sure the additional resources is really justified. Large machines with a lot of cpus would create a lot of kernel threads. Can we do better than that?
Quoted 7 lines
Quoted 3 lines
Would it be possible to have fewer workers (e.g. 1 or one per numa node) and it would perform the work on a dedicated cpu by changing its affinity? Or would that introduce an unacceptable overhead?
Not sure but I can try implementing per-node kthreads and measure the performance of the reclaim path, comparing with the current and with per-cpu approach.
Just to update on this RFC. In my testing I don't see a meaningful improvement from using the kthreads yet. This might be due to my test setup, so I'll keep exploring. Will post the next version only if I get demonstrable improvements.
Thanks!
Quoted 11 lines
Quoted 11 lines
Or would it be possible to update the existing WQ code to use rescuer well before the WQ is completely clogged?
--
Michal Hocko
SUSE Labs--
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].