From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: semaphore redesign
Date: Sat, 28 Feb 2015 10:42:48 -0500 [thread overview]
Message-ID: <20150228154247.GQ23507@brightrain.aerifal.cx> (raw)
In-Reply-To: <alpine.LNX.2.11.1502280111220.10769@monopod.intra.ispras.ru>
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
On Sat, Feb 28, 2015 at 02:21:22AM +0300, Alexander Monakov wrote:
> Hello,
>
> As new cancellation has landed (except that __timedwait fails to propagate
> ECANCELED in addition to ETIMEDOUT and EINTR), I'm happy to post semaphore
> redesign. We discussed this implementation with Rich on IRC once, and
> presently I'm not aware of any issues (finally!), but still testing and
> performance comparison need to be done.
Thanks! I'm attaching a performance testing program I used in the
past. Its time measurement is not very precise, but it should show
large-scale differences. It measures the number of messages that can
be send back and forth between two threads in 2 seconds by cancelling
the two threads after sleep(2).
Some other things we should test for performance:
- Do something like the attached but with multiple threads contending
on semaphores rather than uncontended message passing.
- Time/cycles per call for sem_post and sem_trywait and uncontended
sem_wait -- this looks like it should be an obvious win though.
- Perhaps something to hammer posts and trywait -- it's not clear that
this would model any real-world behavior, but it could show
something interesting anyway.
I doubt we'll see any measurable differences in usage cases where the
futex syscall is expected; it should dominate there.
Rich
[-- Attachment #2: sem_bench.c --]
[-- Type: text/plain, Size: 647 bytes --]
#include <stdio.h>
#include <unistd.h>
#include <pthread.h>
#include <semaphore.h>
static sem_t sem[2];
static long count[2];
static void *func(void *arg)
{
long my_id = (long) arg;
for (;;) {
sem_wait(&sem[my_id]);
count[my_id]++;
sem_post(&sem[1-my_id]);
}
return NULL;
}
int main(void)
{
void *ret;
pthread_t t1, t2;
sem_init(&sem[0], 0, 1);
sem_init(&sem[1], 0, 0);
pthread_create(&t1, NULL, func, (void*) 0);
pthread_create(&t2, NULL, func, (void*) 1);
sleep(2);
pthread_cancel(t1);
pthread_cancel(t2);
pthread_join(t1, &ret);
pthread_join(t2, &ret);
printf("count=%ld\n", count[0] + count[1]);
return 0;
}
next prev parent reply other threads:[~2015-02-28 15:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 2:33 sem_getvalue conformance considerations Rich Felker
2014-08-27 7:05 ` Jens Gustedt
2014-08-27 7:43 ` Rich Felker
2014-08-27 10:43 ` Alexander Monakov
2014-08-27 13:32 ` Alexander Monakov
2014-08-27 19:06 ` Alexander Monakov
2014-08-27 21:06 ` Alexander Monakov
2014-08-28 20:47 ` Alexander Monakov
2014-08-29 22:51 ` Alexander Monakov
2014-08-30 5:12 ` Rich Felker
2014-09-01 17:50 ` Alexander Monakov
2015-02-27 23:21 ` semaphore redesign Alexander Monakov
2015-02-28 15:42 ` Rich Felker [this message]
2015-03-01 18:54 ` Alexander Monakov
2015-03-01 17:30 ` Szabolcs Nagy
2015-03-01 17:50 ` Szabolcs Nagy
2015-03-02 22:40 ` Alexander Monakov
2015-03-02 22:45 ` Rich Felker
2015-03-01 18:24 ` Alexander Monakov
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=20150228154247.GQ23507@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).