I just read up on the Transaction Execution. I now need two things: 1. Aspirin; 2. a nap. I get the general concept, but the restrictions are immense. I guess it is good for a *very* short routine which does not update very much storage. The conditions under which it can abort are a multitude. I wonder exactly what it was that made IBM decide to implement it, as opposed to doing a CPU "spin loop". I guess it is the only way to guarantee that another CPU simply cannot observe an "in flight" set of updates by *any* other code on *any* other CPU.
Now to read up on the other new instructions. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM
