Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758061Ab3CYNrq (ORCPT ); Mon, 25 Mar 2013 09:47:46 -0400 Received: from mail-qc0-f171.google.com ([209.85.216.171]:33676 "EHLO mail-qc0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757818Ab3CYNrn (ORCPT ); Mon, 25 Mar 2013 09:47:43 -0400 MIME-Version: 1.0 In-Reply-To: References: <1363809337-29718-1-git-send-email-riel@surriel.com> Date: Mon, 25 Mar 2013 20:47:42 +0700 Message-ID: Subject: Re: ipc,sem: sysv semaphore scalability From: Emmanuel Benisty To: Linus Torvalds Cc: Rik van Riel , Davidlohr Bueso , Linux Kernel Mailing List , Andrew Morton , hhuang@redhat.com, "Low, Jason" , Michel Lespinasse , Larry Woodman , "Vinod, Chegu" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 953 Lines: 29 On Mon, Mar 25, 2013 at 12:10 AM, Linus Torvalds wrote: > And you never see this problem without Rik's patches? No, never. > Could you bisect > *which* patch it starts with? Are the first four ones ok (the moving > of the locking around, but without the fine-grained ones), for > example? With the first four patches only, I got some X server freeze (just tried once). > Another thing to try might be to enable SLUB debugging (ie make sure that all of > > CONFIG_SLUB_DEBUG=y > CONFIG_SLUB=y > CONFIG_SLUB_DEBUG_ON=y > > are set in your kernel config) My bad, I forgot to enable this in my former build, sorry. Here's what I get now: http://i.imgur.com/G6H8KgD.jpg -- 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/