I believe that one of the primary uses of the transactional execution facility is to solve the ABA problem in a lightweight and efficient manner.
https://en.wikipedia.org/wiki/ABA_problem On Fri, Mar 3, 2017 at 9:10 AM, Ngan, Robert <[email protected]> wrote: > I looked into it, but we don't have the appropriate h/w so I can't play with > it yet. > The unconstrained version may always fail, so you need to always create a > non-transactional version of the code just in case (so this doubles your > coding effort). > The only immediate use I could think of for this facility would be in STAE > code to check dereferencing of potentially corrupted pointers without the > overhead setting up another SPIE/STAE. > > Robert > > -----Original Message----- > From: IBM Mainframe Assembler List [mailto:[email protected]] > On Behalf Of Charles Mills > Sent: Friday, March 03, 2017 09:00 > To: [email protected] > Subject: Re: Transactional Execution - anybody used it? > > I *considered* it for a problem of updating a queue in a multiprocessor > reentrance situation. I ended up solving the problem with CSST which seemed > like a simpler approach. > > Charles > > > -----Original Message----- > From: IBM Mainframe Assembler List [mailto:[email protected]] > On Behalf Of John McKown > Sent: Friday, March 3, 2017 6:32 AM > To: [email protected] > Subject: Re: Transactional Execution - anybody used it? > > OK, I guess I asked my question poorly. And I should not have said anything > about the PLO (instruction, not Mid-East organization) > > So. Has anyone on this forum actually used the TBEGIN and TEND instructions > in their code? I would appreciate knowing what / why they chose to do so. > I'm just trying to understand the real purpose of these instructions on a > PRACTICAL level. Yes, I've read up on "Transactional Memory" on the web. > And how it allows "atomic updates". But I would like a real world example of > why use this vs. the older "atomic" instructions (TSET, CS, CDS, PLO, etc). > > CSC - This is a PRIVATE message - If you are not the intended recipient, > please delete without copying and kindly advise us by e-mail of the mistake > in delivery. NOTE: Regardless of content, this e-mail shall not operate to > bind the Company to any order or other contract unless pursuant to explicit > written agreement or government initiative expressly permitting the use of > e-mail for such purpose.
