From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754163AbdBPJBW (ORCPT ); Thu, 16 Feb 2017 04:01:22 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:50909 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753916AbdBPJBV (ORCPT ); Thu, 16 Feb 2017 04:01:21 -0500 Date: Thu, 16 Feb 2017 10:01:18 +0100 (CET) From: Thomas Gleixner To: Mike Galbraith cc: RT , LKML , Sebastian Andrzej Siewior Subject: Re: [RT] lockdep munching nr_list_entries like popcorn In-Reply-To: <1487235000.5258.48.camel@gmx.de> Message-ID: References: <1487224986.5258.45.camel@gmx.de> <1487235000.5258.48.camel@gmx.de> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 16 Feb 2017, Mike Galbraith wrote: > On Thu, 2017-02-16 at 09:37 +0100, Thomas Gleixner wrote: > > On Thu, 16 Feb 2017, Mike Galbraith wrote: > > > ... > > > swapvec_lock? Oodles of 'em? Nope. > > > > Well, it's a per cpu lock and the lru_cache_add() variants might be called > > from a gazillion of different call chains, but yes, it does not make a lot > > of sense. We'll have a look. > > Adding explicit local_irq_lock_init() makes things heaps better, so > presumably we need better lockdep-foo in DEFINE_LOCAL_IRQ_LOCK(). Bah.