Lines Matching refs:transaction

20 A simple transaction looks like this:
40   /* Retry the transaction if it failed because it conflicted with
49 example, the transaction completes as though it were normal straight-line code
57 transaction, the transaction will be aborted by the CPU.  Register and memory
65 Causes of transaction aborts
77 Performing syscalls from within transaction is not recommended, and can lead
82 remain visible, but depending on the call they may abort your transaction as a
84 invisible, etc.  If you constantly retry a transaction that constantly aborts
92 production use.  Best to queue them up till after the transaction is over.
139            /* Yes, we crashed during a transaction.  Oops. */
150 When in an active transaction that takes a signal, we need to be careful with
159 To avoid this, when taking a signal in an active transaction, we need to use
162 written below the stack required for the rollback.  The transaction is aborted
174 kernel aborted a transaction:
193 GDB and ptrace are not currently TM-aware.  If one stops during a transaction,
194 it looks like the transaction has just started (the checkpointed state is
195 presented).  The transaction cannot then be continued and will take the failure