From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: New optimized normal-type mutex?
Date: Thu, 30 Jul 2015 09:46:49 -0400 [thread overview]
Message-ID: <20150730134649.GC16376@brightrain.aerifal.cx> (raw)
In-Reply-To: <alpine.LNX.2.20.1507301426460.11825@monopod.intra.ispras.ru>
On Thu, Jul 30, 2015 at 02:37:13PM +0300, Alexander Monakov wrote:
> On Thu, 30 Jul 2015, Jens Gustedt wrote:
> > Am Donnerstag, den 30.07.2015, 12:36 +0300 schrieb Alexander Monakov:
> > > That sounds like your testcase simulates a load where you'd be better off with
> > > a spinlock in the first place, no?
> >
> > Hm, this is not a "testcase" in the sense that this is the real code
> > that I'd like to use for the generic atomic lock-full stuff. My test
> > is just using this atomic lock-full thing, with a lot of threads that
> > use the same head of a "lock-free" FIFO implementation. There the
> > inner part in the critical section is just memcpy of some bytes. For
> > reasonable uses of atomics this should be about 16 to 32 bytes that
> > are copied.
> >
> > So this is really a use case that I consider important, and that I
> > would like to see implemented with similar performance.
>
> I acknowledge that that seems like an important case, but you have not
> addressed my main point. With so little work in the critical section, it does
> not make sense to me that you would use something like a normal-type futex-y
> mutex. Even a call/return to grab it gives you some overhead. I'd expect you
> would use a fully inlined spinlock acquisition/release around the memory copy.
No, spinlocks are completely unusable in a POSIX libc that implements
priorities. They will deadlock whenever a lower-priority thread gets
preempted by a higher-priority one while holding the lock.
Rich
next prev parent reply other threads:[~2015-07-30 13:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 23:44 Rich Felker
2015-05-22 7:30 ` Jens Gustedt
2015-05-22 7:51 ` Rich Felker
2015-07-29 12:09 ` Joakim Sindholt
2015-07-29 22:11 ` Jens Gustedt
2015-07-29 23:30 ` Rich Felker
2015-07-29 23:49 ` Jens Gustedt
2015-07-30 0:10 ` Rich Felker
2015-07-30 8:07 ` Jens Gustedt
2015-07-30 9:10 ` Jens Gustedt
2015-07-30 9:36 ` Alexander Monakov
2015-07-30 10:00 ` Jens Gustedt
2015-07-30 11:37 ` Alexander Monakov
2015-07-30 13:46 ` Rich Felker [this message]
2015-07-30 16:07 ` Jens Gustedt
2015-08-03 16:36 ` Alexander Monakov
2015-08-03 19:43 ` Jens Gustedt
2015-08-03 20:05 ` Isaac Dunham
2015-08-04 5:49 ` Jens Gustedt
2015-07-30 13:45 ` Rich Felker
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=20150730134649.GC16376@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).