From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yb0-f198.google.com (mail-yb0-f198.google.com [209.85.213.198]) by kanga.kvack.org (Postfix) with ESMTP id 6B3576B0028 for ; Tue, 10 Apr 2018 16:23:57 -0400 (EDT) Received: by mail-yb0-f198.google.com with SMTP id t11-v6so6472221ybi.3 for ; Tue, 10 Apr 2018 13:23:57 -0700 (PDT) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id s63-v6sor50472ybf.5.2018.04.10.13.23.56 for (Google Transport Security); Tue, 10 Apr 2018 13:23:56 -0700 (PDT) Date: Tue, 10 Apr 2018 13:23:53 -0700 From: Tejun Heo Subject: Re: [RFC] mm, slab: reschedule cache_reap() on the same CPU Message-ID: <20180410202353.GB793541@devbig577.frc2.facebook.com> References: <20180410081531.18053-1-vbabka@suse.cz> <983c61d1-1444-db1f-65c1-3b519ac4d57b@suse.cz> <20180410195247.GQ3126663@devbig577.frc2.facebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Vlastimil Babka Cc: Christopher Lameter , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Joonsoo Kim , David Rientjes , Pekka Enberg , Lai Jiangshan , John Stultz , Thomas Gleixner , Stephen Boyd 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