Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751782Ab3CTU5F (ORCPT ); Wed, 20 Mar 2013 16:57:05 -0400 Received: from g4t0015.houston.hp.com ([15.201.24.18]:33272 "EHLO g4t0015.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751054Ab3CTU5D (ORCPT ); Wed, 20 Mar 2013 16:57:03 -0400 Message-ID: <1363813022.31240.2.camel@buesod1.americas.hpqcorp.net> Subject: Re: ipc,sem: sysv semaphore scalability From: Davidlohr Bueso To: Linus Torvalds Cc: Rik van Riel , Linux Kernel Mailing List , Andrew Morton , hhuang@redhat.com, "Low, Jason" , Michel Lespinasse , Larry Woodman , "Vinod, Chegu" Date: Wed, 20 Mar 2013 13:57:02 -0700 In-Reply-To: References: <1363809337-29718-1-git-send-email-riel@surriel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4 (3.4.4-2.fc17) 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 Content-Length: 1387 Lines: 36 On Wed, 2013-03-20 at 13:49 -0700, Linus Torvalds wrote: > On Wed, Mar 20, 2013 at 12:55 PM, Rik van Riel wrote: > > > > This series makes the sysv semaphore code more scalable, > > by reducing the time the semaphore lock is held, and making > > the locking more scalable for semaphore arrays with multiple > > semaphores. > > The series looks sane to me, and I like how each individual step is > pretty small and makes sense. > > It *would* be lovely to see this run with the actual Swingbench > numbers. The microbenchmark always looked much nicer. Do the > additional multi-semaphore scalability patches on top of Davidlohr's > patches help with the swingbench issue, or are we still totally > swamped by the ipc lock there? Yes, I'm testing this patchset with my swingbench workloads. I should have some numbers by today or tomorrow. > > Maybe there were already numbers for that, but the last swingbench > numbers I can actually recall was from before the finer-grained > locking.. Right, I couldn't get Oracle to run on the with the previous patches, hopefully the bug(s) are now addressed. Thanks, Davidlohr -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/