Facilitating transaction completion subsequent to repeated aborts of the transaction

• US 9,367,378 B2
• Filed: 03/03/2013
• Issued: 06/14/2016
• Est. Priority Date: 06/15/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Belmar, Brenton F., Jacobi, Christian, Philley, Randall W., Slegel, Timothy J.
• Primary Examiner(s): Pham, Tuan A
• Application Number:
  US13/783,316
• Publication Number:
  US 20130339330A1
• Time in Patent Office: 1,199 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/0721 within a central processing unit [CPU]
• CPC Class Codes: G06F 11/076 by exceeding a count or rate limit, e.g. word- or bit count limit
• CPC Class Codes: G06F 13/24 using interrupt G06F13/32 takes precedence
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 9/466 Transaction processing

Abstract

Processing of transactions within a computing environment is facilitated by taking actions to increase the chances of successfully executing a transaction. A counter is maintained that provides a count of how often a transaction has aborted. The counter increments the count each time the transaction is aborted, and it is reset to zero upon successful completion of the transaction or an interruption leading to no more re-executions of the transaction. If the count reaches a threshold value, then an interrupt is presented and transaction execution is unsuccessful. However, before the count reaches the threshold, a number of actions may be taken to increase the chances of successfully executing the transaction. These actions include actions to be performed within the processor executing the transaction, and/or actions to be performed against conflicting processors.

Claims

1. A method of facilitating processing within a computing environment, said method comprising:

tracking, by a processor of the computing environment, a number of times a transaction executing within the processor aborts, the transaction effectively delaying committing transactional stores to main memory until completion of a selected transaction, and the tracking employing a counter within the processor to track the number of aborts of the transaction;

determining whether the transaction has successfully completed, and based on the transaction successfully completing, automatically resetting the counter to a predefined value;

based on the transaction aborting, automatically resetting the counter to the predefined value based on an interruption action, wherein the automatically resetting the counter to the predefined value is based on one of the following;

reaching by the counter a threshold number of aborts for the transaction causing an interrupt to be presented for the transaction, the counter to track the number of aborts of the transaction;

determining the abort of the transaction is due to an interruption; and

based on the transaction aborting for a reason other than an interruption, determining whether the counter has reached the threshold number of aborts, and based on the counter not reaching the threshold number of aborts, re-executing the transaction via a transaction begin instruction.

2. The method of claim 1, wherein the transaction is a constrained transaction having a plurality of restrictions associated therewith, and wherein the transaction begin instruction is a transaction begin constrained instruction.

3. The method of claim 1, further comprising based on the transaction aborting for a reason other than an interruption, determining whether the counter has reached the threshold number of aborts, and based on the counter not reaching the threshold number of aborts, incrementing the counter, and setting a program instruction address to the transaction begin instruction to re-execute the transaction.

4. The method of claim 1, further comprising based on the transaction aborting for a reason other than an interruption, determining whether the counter has reached the threshold number of aborts, and based on the counter not reaching the threshold number of aborts, determining whether an action is to be taken to facilitate successful completion of the transaction on re-execution.

5. The method of claim 4, further comprising:

selecting one or more actions based on the determining indicating an action is to be performed; and

performing the selected one or more actions.

6. The method of claim 5, wherein the one or more actions comprise one or more actions of the following actions:

disabling branch prediction, disabling speculative instruction fetching, disabling super-scalar dispatching, disabling out-of-order execution, fetching cache misses exclusively, or executing a single instruction through an instruction pipeline.

7. The method of claim 6, wherein the following actions further comprise using a semaphore to block out one or more other processors.

8. The method of claim 5, wherein the selecting comprises choosing an action based on one or more of a value of the counter and a reason for the abort.

9. The method of claim 1, wherein the counter is a hardware counter.