Re: [PATCH] mm, slab: reschedule cache_reap() on the same CPU

On 04/12/2018 02:47 AM, Minchan Kim wrote: > On Wed, Apr 11, 2018 at 09:00:07AM +0200, Vlastimil Babka wrote: >> cache_reap() is initially scheduled in start_cpu_timer() via >> schedule_delayed_work_on(). But then the next iterations are scheduled via >> schedule_delayed_work(), i.e. using

Re: [PATCH] mm, slab: reschedule cache_reap() on the same CPU

On 04/12/2018 02:47 AM, Minchan Kim wrote: > On Wed, Apr 11, 2018 at 09:00:07AM +0200, Vlastimil Babka wrote: >> cache_reap() is initially scheduled in start_cpu_timer() via >> schedule_delayed_work_on(). But then the next iterations are scheduled via >> schedule_delayed_work(), i.e. using

Re: [PATCH] mm, slab: reschedule cache_reap() on the same CPU

On Wed, Apr 11, 2018 at 09:00:07AM +0200, Vlastimil Babka wrote: > cache_reap() is initially scheduled in start_cpu_timer() via > schedule_delayed_work_on(). But then the next iterations are scheduled via > schedule_delayed_work(), i.e. using WORK_CPU_UNBOUND. > > Thus since commit ef557180447f

Re: [PATCH] mm, slab: reschedule cache_reap() on the same CPU

On Wed, Apr 11, 2018 at 09:00:07AM +0200, Vlastimil Babka wrote: > cache_reap() is initially scheduled in start_cpu_timer() via > schedule_delayed_work_on(). But then the next iterations are scheduled via > schedule_delayed_work(), i.e. using WORK_CPU_UNBOUND. > > Thus since commit ef557180447f

Re: [PATCH] mm, slab: reschedule cache_reap() on the same CPU

On Wed, 11 Apr 2018, Pekka Enberg wrote: > Acked-by: Pekka Enberg Good to hear from you again. Acked-by: Christoph Lameter

Re: [PATCH] mm, slab: reschedule cache_reap() on the same CPU

On Wed, 11 Apr 2018, Pekka Enberg wrote: > Acked-by: Pekka Enberg Good to hear from you again. Acked-by: Christoph Lameter

Re: [PATCH] mm, slab: reschedule cache_reap() on the same CPU

On 11/04/2018 10.00, Vlastimil Babka wrote: cache_reap() is initially scheduled in start_cpu_timer() via schedule_delayed_work_on(). But then the next iterations are scheduled via schedule_delayed_work(), i.e. using WORK_CPU_UNBOUND. Thus since commit ef557180447f ("workqueue: schedule

Re: [PATCH] mm, slab: reschedule cache_reap() on the same CPU

On 11/04/2018 10.00, Vlastimil Babka wrote: cache_reap() is initially scheduled in start_cpu_timer() via schedule_delayed_work_on(). But then the next iterations are scheduled via schedule_delayed_work(), i.e. using WORK_CPU_UNBOUND. Thus since commit ef557180447f ("workqueue: schedule

[PATCH] mm, slab: reschedule cache_reap() on the same CPU

cache_reap() is initially scheduled in start_cpu_timer() via schedule_delayed_work_on(). But then the next iterations are scheduled via schedule_delayed_work(), i.e. using WORK_CPU_UNBOUND. Thus since commit ef557180447f ("workqueue: schedule WORK_CPU_UNBOUND work on wq_unbound_cpumask CPUs")

[PATCH] mm, slab: reschedule cache_reap() on the same CPU

cache_reap() is initially scheduled in start_cpu_timer() via schedule_delayed_work_on(). But then the next iterations are scheduled via schedule_delayed_work(), i.e. using WORK_CPU_UNBOUND. Thus since commit ef557180447f ("workqueue: schedule WORK_CPU_UNBOUND work on wq_unbound_cpumask CPUs")