From: Mike Galbraith <efault@gmx.de>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>,
Davidlohr Bueso <davidlohr.bueso@hp.com>,
hhuang@redhat.com, Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/6] ipc/sem.c: performance improvements, FIFO
Date: Sat, 15 Jun 2013 10:36:20 +0200 [thread overview]
Message-ID: <1371285380.5789.42.camel@marge.simpson.net> (raw)
In-Reply-To: <1371281407.5789.24.camel@marge.simpson.net>
On Sat, 2013-06-15 at 09:30 +0200, Mike Galbraith wrote:
> Gee, just trying to flip back to a single semaphore lock mode if you had
> to do the global wait thing fixed up -rt.
But master wants a sharper rock tossed at it, it's still unstable.
Result matrix:
Thread 0: 11190947
Thread 1: 11743861
Thread 2: 10039223
Thread 3: 9776111
Thread 4: 9734815
Thread 5: 9941121
Thread 6: 11604118
Thread 7: 11716281
Thread 8: 9828587
Thread 9: 9589199
...
And that's one of the better samples. Probably -rt sleepy locks help
get us flipped back to single sem lock mode.
Hohum. On the bright side, -rt gets to scale better than mainline for a
little while, that's kinda different.
-Mike
next prev parent reply other threads:[~2013-06-15 8:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 17:16 Manfred Spraul
2013-06-10 17:16 ` [PATCH 1/6] ipc/util.c, ipc_rcu_alloc: cacheline align allocation Manfred Spraul
2013-06-10 17:16 ` [PATCH 2/6] ipc/sem.c: cacheline align the semaphore structures Manfred Spraul
2013-06-10 17:16 ` [PATCH 3/6] ipc/sem: seperate wait-for-zero and alter tasks into seperate queues Manfred Spraul
2013-06-10 17:16 ` [PATCH 4/6] ipc/sem.c: Always use only one queue for alter operations Manfred Spraul
2013-06-10 17:16 ` [PATCH 5/6] ipc/sem.c: Replace shared sem_otime with per-semaphore value Manfred Spraul
2013-06-10 17:16 ` [PATCH 6/6] ipc/sem.c: Rename try_atomic_semop() to perform_atomic_semop(), docu update Manfred Spraul
2013-06-14 15:38 ` [PATCH 0/6] ipc/sem.c: performance improvements, FIFO Manfred Spraul
2013-06-14 19:05 ` Mike Galbraith
2013-06-15 5:27 ` Manfred Spraul
2013-06-15 5:48 ` Mike Galbraith
2013-06-15 7:30 ` Mike Galbraith
2013-06-15 8:36 ` Mike Galbraith [this message]
2013-06-15 11:10 ` Manfred Spraul
2013-06-15 11:37 ` Mike Galbraith
2013-06-18 6:48 ` Mike Galbraith
2013-06-18 7:14 ` Mike Galbraith
2013-06-19 12:57 ` Mike Galbraith
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=1371285380.5789.42.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=davidlohr.bueso@hp.com \
--cc=hhuang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.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
Powered by JetHome