This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Lock Elision / Transaction ABI discussion
- From: David Collier-Brown <davec-b at rogers dot com>
- To: libc-alpha at sourceware dot org
- Date: Tue, 17 Sep 2013 12:33:23 -0400
- Subject: Re: Lock Elision / Transaction ABI discussion
- Authentication-results: sourceware.org; auth=none
- References: <1379367939 dot 29887 dot ezmlm at sourceware dot org>
- Reply-to: davecb at spamcop dot net
We hit this in the ARPA days, too. The possible cases we found were
encoded by Postel as "replies" in RFC 821:
1 - positive preliminary reply, AKA "partial success, continue or abort"
2 - positive completion. AKA "success"
3 - positive intermediate reply, almost the same as "partial success",
but it assumes you must continue
4 - transient negative, AKA "try again later"
5 - permanent failure, AKA "failure"
No-one seems to have used 1, so I implemented it as "information
message" in GCOS SMTP and the arpakit.
I suspect 2-5 are the necessary and sufficient states for
communications, and what we'd now call a pattern... from which we might
infer a similar, sufficient pattern for locking, one that isn't likely
to paint us into a corner later.
--dave (admittedly feeling somewhat old (;-)) c-b
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
(416) 223-8968