From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] userspace semlocks
Date: Mon, 23 Sep 2013 17:19:25 -0400 [thread overview]
Message-ID: <d28d3f9a28454e67a15e36ee8e7b28b9@ladd.quanstro.net> (raw)
In-Reply-To: <CAOw7k5gmTxRYWPQxYcEUqpYuL2+n_0imBPcZyEWq0Y88cav-mw@mail.gmail.com>
> On 22 September 2013 03:55, erik quanstrom <quanstro@quanstro.net> wrote:
>
> >
> > new 1.55e10 O=10 M=8
> > old 2.74e10
> >
> > new 3.64e10 O=0 M=8
> > old 5.14e10
> >
> > am i doing something fundamental wrong, or are the new locks substantially
> > slower than the old ones?
> >
>
> In those cases, the new times seem to be quite a bit faster, more than they
> are slower in the cases you found
> slower, which involved only one process (if I understand the tests)
data entry error. swap new and old for these cases. i confused myself
by not calling them semlocks and taslocks in the email.
- erik
next prev parent reply other threads:[~2013-09-23 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-22 2:55 erik quanstrom
2013-09-22 5:48 ` Bruce Ellis
2013-09-23 13:56 ` erik quanstrom
2013-09-23 21:11 ` Charles Forsyth
2013-09-23 21:19 ` erik quanstrom [this message]
2013-09-23 22:27 ` erik quanstrom
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=d28d3f9a28454e67a15e36ee8e7b28b9@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).