From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756631AbbCFTpK (ORCPT ); Fri, 6 Mar 2015 14:45:10 -0500 Received: from cantor2.suse.de ([195.135.220.15]:60632 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756002AbbCFTpI (ORCPT ); Fri, 6 Mar 2015 14:45:08 -0500 Message-ID: <1425671101.19505.51.camel@stgolabs.net> Subject: Re: sched: softlockups in multi_cpu_stop From: Davidlohr Bueso To: Linus Torvalds Cc: Jason Low , Ingo Molnar , Sasha Levin , Peter Zijlstra , LKML , Dave Jones Date: Fri, 06 Mar 2015 11:45:01 -0800 In-Reply-To: References: <54F41516.6060608@oracle.com> <54F98F1F.3080107@oracle.com> <20150306123233.GA9972@gmail.com> <1425662342.19505.41.camel@stgolabs.net> <1425668223.2475.94.camel@j-VirtualBox> <1425669643.19505.46.camel@stgolabs.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.9 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2015-03-06 at 11:32 -0800, Linus Torvalds wrote: > Basically, to me, the whole "if a lock is so contended that we need to > play locking games, then we should look at why we *use* the lock, > rather than at the lock itself" is a religion. Oh absolutely, I'm only mentioning the locking primitive side of mmap_sem, for which minor optimizations will _never_ solve the actual scalability issues. But yes, point taken. Thanks, Davidlohr