From: Rik van Riel <riel@surriel.com>
To: sedat.dilek@gmail.com
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
x86@kernel.org, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Paul McKenney <paul.mckenney@linaro.org>,
DRI <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@redhat.com>,
Davidlohr Bueso <davidlohr.bueso@hp.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Emmanuel Benisty <benisty.e@gmail.com>
Subject: Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
Date: Fri, 19 Apr 2013 15:19:03 -0400 [thread overview]
Message-ID: <517198A7.8020904@surriel.com> (raw)
In-Reply-To: <CA+icZUUp84vzF_0n77wsJ6dBOS26vSRCXaFUDbCQi-wG0b-Osg@mail.gmail.com>
On 04/19/2013 02:53 PM, Sedat Dilek wrote:
> On Fri, Apr 19, 2013 at 6:43 PM, Sedat Dilek <sedat.dilek@gmail.com> 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 :)
next prev parent reply other threads:[~2013-04-19 19:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+icZUVWC+Rgd9wh4Z4CPZkEa9Pm2=2udnY5=UD1nnH0Wot1pQ@mail.gmail.com>
2013-04-18 19:48 ` linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ] Daniel Vetter
2013-04-18 21:59 ` Sedat Dilek
2013-04-19 10:19 ` Sedat Dilek
[not found] ` <CA+icZUXjTGSG+tejOAFgXr8EpKd7dL=-W41ha_-0N=roAxN3eg@mail.gmail.com>
2013-04-19 16:43 ` Sedat Dilek
2013-04-19 18:53 ` Sedat Dilek
2013-04-19 19:19 ` Rik van Riel [this message]
2013-04-19 20:12 ` Davidlohr Bueso
[not found] ` <CA+icZUVjx7pDJWo3tGxX3ANXtiTP0_Q1YyOowANhn1wzcSgWaA@mail.gmail.com>
2013-04-19 21:24 ` Linus Torvalds
2013-04-19 21:39 ` Paul E. McKenney
2013-04-19 22:12 ` Sedat Dilek
2013-04-19 22:34 ` Sedat Dilek
2013-04-19 22:50 ` Linus Torvalds
2013-04-19 22:55 ` Sedat Dilek
2013-04-19 23:02 ` Linus Torvalds
2013-04-20 0:06 ` Sedat Dilek
2013-04-20 0:19 ` Sedat Dilek
2013-04-20 12:46 ` Sedat Dilek
2013-04-20 15:59 ` Rik van Riel
2013-04-20 17:04 ` Sedat Dilek
2013-04-20 20:00 ` Davidlohr Bueso
2013-04-20 21:03 ` Sedat Dilek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=517198A7.8020904@surriel.com \
--to=riel@surriel.com \
--cc=airlied@redhat.com \
--cc=benisty.e@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=davidlohr.bueso@hp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.mckenney@linaro.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).