From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: "Mark H. Weaver" <mhw@netris.org>, guile-devel@gnu.org
Subject: Re: port threadsafety redux
Date: Wed, 04 Mar 2015 11:18:05 +0100 [thread overview]
Message-ID: <87sidljcbm.fsf@gnu.org> (raw)
In-Reply-To: <87vbj816sg.fsf@pobox.com> (Andy Wingo's message of "Wed, 11 Feb 2015 22:23:43 +0100")
Andy Wingo <wingo@pobox.com> skribis:
> Namely, ports can have associated recursive mutexes. They can be in a
> mode in which every operation on a port grabs the mutex. The interface
> to set a port into unlocked mode (à la fsetlocking) is unimplemented,
> but the machinery is there.
>
> This change fixed the crashes I was seeing, but it slows down port
> operations. For an intel chip from a couple years ago the slowdown was
> something on the order of 3x, for a tight putchar() loop; for Loongson
> it could be as bad as 26x. Mark was unhappy with this.
Thanks for bringing up the issue. I’d like to hear what Mark thinks.
:-)
Ludo’.
prev parent reply other threads:[~2015-03-04 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 21:23 port threadsafety redux Andy Wingo
2015-02-13 18:35 ` David Pirotte
2015-02-17 12:11 ` Chris Vine
2015-03-04 10:18 ` Ludovic Courtès [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sidljcbm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@pobox.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).