From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752659AbbFVUG4 (ORCPT ); Mon, 22 Jun 2015 16:06:56 -0400 Received: from mail-ig0-f181.google.com ([209.85.213.181]:36991 "EHLO mail-ig0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751233AbbFVUGs (ORCPT ); Mon, 22 Jun 2015 16:06:48 -0400 MIME-Version: 1.0 In-Reply-To: <20150622121623.291363374@infradead.org> References: <20150622121623.291363374@infradead.org> Date: Mon, 22 Jun 2015 13:06:47 -0700 X-Google-Sender-Auth: wpDkWvqGN2c3wMYcJNKzvgxKfL8 Message-ID: Subject: Re: [RFC][PATCH 00/13] percpu rwsem -v2 From: Linus Torvalds To: Peter Zijlstra Cc: Oleg Nesterov , Paul McKenney , Tejun Heo , Ingo Molnar , Linux Kernel Mailing List , der.herr@hofr.at, Davidlohr Bueso , Rik van Riel , Al Viro Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 22, 2015 at 5:16 AM, Peter Zijlstra wrote: > > It further removes the stop_machine lglock usage, and with it kills lglocks. Ok. With all the conversions, and removal of lglock, my dislike of this goes away. I'm somewhat worried about Daniel's report about "building a kernel with 'make -j200' was extreme slow", but that may be due to something else (does the machine have enough memory for "make -j200"? The kernel compile parallelizes so well, and gcc uses so much memory, that you need a *lot* of memory to use things like "-j200"). But assuming that gets sorted out, and somebody looks at the few file locking performance issues, I have no objections to this series any more. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in Please read the FAQ at http://www.tux.org/lkml/