Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753519Ab3DSTTe (ORCPT ); Fri, 19 Apr 2013 15:19:34 -0400 Received: from shelob.surriel.com ([74.92.59.67]:49822 "EHLO shelob.surriel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752494Ab3DSTTd (ORCPT ); Fri, 19 Apr 2013 15:19:33 -0400 Message-ID: <517198A7.8020904@surriel.com> Date: Fri, 19 Apr 2013 15:19:03 -0400 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: sedat.dilek@gmail.com CC: Daniel Vetter , Stephen Rothwell , linux-next , Linux Kernel Mailing List , x86@kernel.org, Ingo Molnar , Thomas Gleixner , Paul McKenney , Paul McKenney , DRI , Dave Airlie , Davidlohr Bueso , Linus Torvalds , Emmanuel Benisty Subject: Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ] References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1486 Lines: 47 On 04/19/2013 02:53 PM, Sedat Dilek wrote: > On Fri, Apr 19, 2013 at 6:43 PM, Sedat Dilek wrote: > >> I tried to switch from SLUB to SLAB... >> >> ...and also from VIRT_CPU_ACCOUNTING_GEN to TICK_CPU_ACCOUNTING. >> >> 2x NOPE. >> >> In one kernel-build I saw in my console... >> >> semop(1): encountered an error: Identifier removed >> >> ...if this says sth. to you. >> > [ CC folks from below thread ] > > I have found a thread called "Re: ipc,sem: sysv semaphore scalability" > on LKML with a screenshot that shows the same call-trace. > I followed it a bit. > There is a patch in [3]... unconfirmed. > > Comments on the rcu read-lock and "sem_lock()" vs "sem_unlock()" from Linus. > > What's the status of this discussion? > > - Sedat - > > [1] https://lkml.org/lkml/2013/3/30/6 > [2] http://i.imgur.com/uk6gmq1.jpg > [3] https://lkml.org/lkml/2013/3/31/12 > [4] https://lkml.org/lkml/2013/3/31/77 > I am at a conference right now, but when I get back I will check linux-next vs. all the fixes from the semaphore scalability email thread. I will gather up the not-yet-in-linux-next fixes, and will send them to Andrew for inclusion. No guarantee that those fixes are related to your problem, of course :) -- 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/