From: Florian Weimer <fweimer@redhat.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: libc-alpha@sourceware.org, gcc-help@gcc.gnu.org,
"Paul E. McKenney" <paulmck@kernel.org>,
Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
Subject: Re: Help needed for glibc software transaction memory algorithm
Date: Wed, 05 Jan 2022 12:38:46 +0100 [thread overview]
Message-ID: <87y23ue7jt.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20220104221427.GO3294453@arm.com> (Szabolcs Nagy's message of "Tue, 4 Jan 2022 22:14:27 +0000")
* Szabolcs Nagy:
> this reminds me the discussion in section 4 and 5 of
>
> https://www.hpl.hp.com/techreports/2012/HPL-2012-68.pdf
>
> there are no 2 data copies here but i think the reasoning
> about the synchronization may apply.
Yes, I'll reference that and put in the acquire fence. Thanks.
Florian
next prev parent reply other threads:[~2022-01-05 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 14:12 Florian Weimer
2022-01-04 22:14 ` Szabolcs Nagy
2022-01-05 11:38 ` Florian Weimer [this message]
2022-01-05 13:07 ` Tulio Magno Quites Machado Filho
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=87y23ue7jt.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=paulmck@kernel.org \
--cc=szabolcs.nagy@arm.com \
--cc=tuliom@linux.vnet.ibm.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).