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 09:30:07 +0200 [thread overview]
Message-ID: <1371281407.5789.24.camel@marge.simpson.net> (raw)
In-Reply-To: <1371275319.5789.13.camel@marge.simpson.net>
On Sat, 2013-06-15 at 07:48 +0200, Mike Galbraith wrote:
> On Sat, 2013-06-15 at 07:27 +0200, Manfred Spraul wrote:
>
> > Assume there is one op (semctl(), whatever) that acquires the global
> > lock - and a continuous stream of simple ops.
> > - spin_is_locked() returns true due to the semctl().
> > - then simple ops will switch to spin_lock(&sma->sem_perm.lock).
> > - since the spinlock is acquired, the next operation will get true from
> > spin_is_locked().
> >
> > It will stay that way around - as long as there is at least one op
> > waiting for sma->sem_perm.lock.
> > With enough cpus, it will stay like this forever.
>
> Yup, pondered that yesterday, scratching my head over how to do better.
> Hints highly welcome. Maybe if I figure out how to scratch dual lock
> thingy properly for -rt, non-rt will start acting sane too, as that spot
> seems to be itchy in both kernels.
Gee, just trying to flip back to a single semaphore lock mode if you had
to do the global wait thing fixed up -rt. 10 consecutive sem-waitzero 5
8 64 runs with the 3.8-rt9 kernel went like so, which is one hell of an
improvement.
Result matrix:
Thread 0: 20209311
Thread 1: 20255372
Thread 2: 20082611
...
Thread 61: 20162924
Thread 62: 20048995
Thread 63: 20142689
I must have screwed up something :)
static inline int sem_lock(struct sem_array *sma, struct sembuf *sops,
int nsops)
{
struct sem *sem;
int locknum;
if (nsops == 1 && !sma->complex_count) {
sem = sma->sem_base + sops->sem_num;
/*
* Another process is holding the global lock on the
* sem_array; we cannot enter our critical section,
* but have to wait for the global lock to be released.
*/
if (unlikely(spin_is_locked(&sma->sem_perm.lock))) {
spin_lock(&sma->sem_perm.lock);
if (sma->complex_count)
goto wait_array;
/*
* Acquiring our sem->lock under the global lock
* forces new complex operations to wait for us
* to exit our critical section.
*/
spin_lock(&sem->lock);
spin_unlock(&sma->sem_perm.lock);
} else {
/* Lock just the semaphore we are interested in. */
spin_lock(&sem->lock);
/*
* If sma->complex_count was set prior to acquisition,
* we must fall back to the global array lock.
*/
if (unlikely(sma->complex_count)) {
spin_unlock(&sem->lock);
goto lock_array;
}
}
locknum = sops->sem_num;
} else {
int i;
/*
* Lock the semaphore array, and wait for all of the
* individual semaphore locks to go away. The code
* above ensures no new single-lock holders will enter
* their critical section while the array lock is held.
*/
lock_array:
spin_lock(&sma->sem_perm.lock);
wait_array:
for (i = 0; i < sma->sem_nsems; i++) {
sem = sma->sem_base + i;
#ifdef CONFIG_PREEMPT_RT_BASE
if (spin_is_locked(&sem->lock))
#endif
spin_unlock_wait(&sem->lock);
}
locknum = -1;
if (nsops == 1 && !sma->complex_count) {
sem = sma->sem_base + sops->sem_num;
spin_lock(&sem->lock);
spin_unlock(&sma->sem_perm.lock);
locknum = sops->sem_num;
}
}
return locknum;
}
Not very pretty, but it works markedly better.
next prev parent reply other threads:[~2013-06-15 7:30 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 [this message]
2013-06-15 8:36 ` Mike Galbraith
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=1371281407.5789.24.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