[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180410202353.GB793541@devbig577.frc2.facebook.com>
Date: Tue, 10 Apr 2018 13:23:53 -0700
From: Tejun Heo <tj@...nel.org>
To: Vlastimil Babka <vbabka@...e.cz>
Cc: Christopher Lameter <cl@...ux.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Joonsoo Kim <iamjoonsoo.kim@....com>,
David Rientjes <rientjes@...gle.com>,
Pekka Enberg <penberg@...nel.org>,
Lai Jiangshan <jiangshanlai@...il.com>,
John Stultz <john.stultz@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Stephen Boyd <sboyd@...nel.org>
Subject: Re: [RFC] mm, slab: reschedule cache_reap() on the same CPU
Hello,
On Tue, Apr 10, 2018 at 10:13:33PM +0200, Vlastimil Babka wrote:
> > For percpu work items, they'll keep executing on the same cpu it
> > started on unless the cpu goes down while executing.
>
> Right, but before this patch, with just schedule_delayed_work() i.e.
> non-percpu? If such work can migrate in the middle, the slab bug is
> potentially much more serious.
That's still per-cpu. The only time the local binding breaks is when
the kernel is explicitly told to do so through explicit unbound_mask
or force_rr debug option.
Thanks.
--
tejun
Powered by blists - more mailing lists