Transaction attributes specified by the application. More...
Data Fields | |
int | id |
Application-specific identifier for the transaction. | |
unsigned int | read_only: 1 |
Indicates whether the transaction is read-only. | |
unsigned int | no_retry: 1 |
Indicates that the transaction should not retry execution using sigsetjmp() after abort. |
Transaction attributes specified by the application.
int stm_tx_attr::id |
Application-specific identifier for the transaction.
Typically, each transactional construct (atomic block) should have a different identifier. This identifier can be used by the infrastructure for improving performance, for instance by not scheduling together atomic blocks that have conflicted often in the past.
unsigned int stm_tx_attr::no_retry |
Indicates that the transaction should not retry execution using sigsetjmp() after abort.
If no attributes are specified when starting a transaction, the default behavior is to retry.
unsigned int stm_tx_attr::read_only |
Indicates whether the transaction is read-only.
This information is used as a hint. If a read-only transaction performs a write, it is aborted and restarted in read-write mode. In that case, the value of the read-only flag is changed to false. If no attributes are specified when starting a transaction, it is assumed to be read-write.