On Tue, 2015-04-14 at 17:04 +0200, Denys Vlasenko wrote: > On 04/14/2015 04:21 PM, Eric Dumazet wrote: > > On Tue, 2015-04-14 at 15:57 +0200, Denys Vlasenko wrote: > > > >> My allyesconfig, with BUG_ON's commented out: > >> > > > > Right. But I can tell you nobody uses lockdep on a production kernel. > > > > Here, at Google, we get what I described. > > I'm trying to get to the .config which generates a small function. > > So far, with LOCKDEP off, it is still this big: >
If you read exactly what I wrote, you'll understand that at Google, rcu_read_lock() & rcu_read_unlock() are nop. Your patch is based on a worst case scenario, and will slow down our use case. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
