mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: cpuset/affinity interfaces and TSX lock elision in musl
Date: Fri, 17 May 2013 13:28:02 +0200	[thread overview]
Message-ID: <20130517112802.GA6699@port70.net> (raw)
In-Reply-To: <CAPLrYERdrp6uv6NyhjRzFjXO4ae_1Gkfn6m_n+ZHAKH50yLqjQ@mail.gmail.com>

* Daniel Cegie?ka <daniel.cegielka@gmail.com> [2013-05-17 09:41:18 +0200]:
> >> 2) The upcoming glibc will have support for TSX lock elision.
> >>
> >> http://en.wikipedia.org/wiki/Transactional_Synchronization_Extensions
> >>
> >> http://lwn.net/Articles/534761/
> >>
> >> Are there any outlook that we can support TSX lock elision in musl?
> >
> > I was involved in the discussions about lock elision on the glibc
> > mailing list, and from what I could gather, it's a pain to implement
> > and whether it brings you any benefit is questionable.
> 
> There is currently no hardware support, so the tests were done in the
> emulator. It's too early to say there's is no performance gain.
> 

it's not the lock performance that's questionable
but the benefits

locks should not be the bottleneck in applications
unless there is too much shared state on hot paths,
which is probably a design bug or a special use-case
for which non-standard synchronization methods may
be better anyway

for the implementation costs check the glibc
discussion where rich pointed out conformance
issues in the original design

http://article.gmane.org/gmane.comp.lib.glibc.alpha/29240


  reply	other threads:[~2013-05-17 11:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 16:37 Daniel Cegiełka
2013-05-16 20:36 ` Rich Felker
2013-05-17  4:49   ` Rob Landley
2013-05-17  5:01     ` Rich Felker
2013-05-19  4:05       ` Rob Landley
2013-05-17  7:41   ` Daniel Cegiełka
2013-05-17 11:28     ` Szabolcs Nagy [this message]
2013-05-17 17:29       ` Rich Felker
2013-05-19  4:40         ` Rob Landley
2013-05-19 20:51           ` Rich Felker
2013-05-19  4:12     ` Rob Landley

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=20130517112802.GA6699@port70.net \
    --to=nsz@port70.net \
    --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).