System and method for memory synchronization of a multi-core system
US-2017337256-A1 · Nov 23, 2017 · US
US9870384B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9870384-B2 |
| Application number | US-201213435281-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 30, 2012 |
| Priority date | Mar 30, 2012 |
| Publication date | Jan 16, 2018 |
| Grant date | Jan 16, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems, methods, and products for database system transaction management are provided herein. One aspect provides for annotating via a computing device at least one data object residing on the computing device utilizing at least one transaction tag, the at least one transaction tag being configured to indicate a status of an associated data object; processing at least one database transaction utilizing a transactional memory process, wherein access to the at least one data object is determined based on the status of the at least one data object; and updating the status of the at least one data object responsive to an attempted access of the at least one data object by the at least one database transaction. Other embodiments and aspects are also described herein.
Opening claim text (preview).
What is claimed is: 1. A system comprising: at least one processor; and a memory device operatively connected to the at least one processor; wherein, responsive to execution of program instructions accessible to the at least one processor, the at least one processor is configured to: annotate at least one data object utilizing at least one transactional tag, the at least one transactional tag being configured to indicate a status of the at least one data object, wherein the status indicates the accessibility of the at least one data object; the at least one transactional tag further being associated with one or more data structures configured to support operation of a transactional memory process; process at least one database transaction using the at least one data object utilizing a transactional memory process, wherein access to the at least one data object is determined based on the status of the at least one data object, wherein to process comprises updating the transactional tag of the at least one data object to reserve access privilege of the at least one data object and setting access to the at least one data object as lock free, wherein the access privilege comprises a right to attempt access and operation of the at least one data object; update the status of at least one data object, having a status of uncommitted, responsive to an attempted access of the at least one uncommitted data object by the at least one database transaction having reserved access to the at least one data object, wherein to update the status comprises modifying the transactional tag of the at least one uncommitted data object by marking the at least one uncommitted data object as accessed; and blocking access to the at least one data object by a database transaction not having reserved access to the at least one data object. 2. The system according to claim 1 , wherein the at least one processor is further configured to define at least one application programming interface configured to enable a transaction declaration on data annotated with a transactional tag. 3. The system according to claim 1 , wherein the status of the at least one data object is updated via hardware transaction management. 4. The system according to claim 3 , wherein hardware transaction management handles updating optimistically lock-free. 5. The system according to claim 1 , wherein the at least one transactional tag comprises an active read counter and an active write counter. 6. The system according to claim 1 , wherein the at least one transactional tag is transparent to applications invoking database transactions. 7. The system according to claim 1 , wherein the update of the status of the at least one data object is undone responsive to completion of access to the at least one data object. 8. The system according to claim 1 , wherein access to a plurality of data objects may be grouped. 9. The system according to claim 1 , wherein access to a grouped plurality of data objects is granted on an all-or-nothing basis. 10. The system according to claim 1 , wherein the at least one data object is defined within a database comprising table, page, and row elements. 11. A method comprising: annotating via a computing device at least one data object residing on the computing device utilizing at least one transactional tag, the at least one transactional tag being configured to indicate a status of an associated data object, wherein the status indicates the accessibility of the at least one data object; the at least one transactional tag further being associated with one or more data structures configured to support operation of a transactional memory process; processing at least one database transaction using the at least one data object utilizing a transactional memory process, wherein access to the at least one data object is determined based on the status of the at least one data object, wherein to process comprises updating the transactional tag of the at least one data object to reserve access privilege of the at least one data object and setting access to the at least one data object as lock free, wherein the access privilege comprises a right to attempt access and operation of the at least one data object; updating the status of at least one data object, having a status of uncommitted, responsive to an attempted access of the at least one uncommitted data object by the at least one database transaction having reserved access to the at least one data object, wherein updating the status comprises modifying the transactional tag of the at least one uncommitted data object by marking the at least one uncommitted data object as accessed; and blocking access to the at least one data object by a database transaction not having reserved access to the at least one data object. 12. The method according to claim 11 , further comprising defining at least one application programming interface configured to enable a transaction declaration on data annotated with a transactional tag. 13. The method according to claim 11 , wherein the status of the at least one data object is updated via hardware transaction management. 14. The method according to claim 13 , wherein hardware transaction management handles updating optimistically lock-free. 15. The method according to claim 11 , wherein the at least one transactional tag comprises an active read counter and an active write counter. 16. The method according to claim 11 , wherein the at least one transactional tag is transparent to applications invoking database transactions. 17. The method according to claim 11 , wherein the update of the status of the at least one data object is undone responsive to completion of access to the at least one data object. 18. The method according to claim 11 , wherein access to a plurality of data objects may be grouped. 19. The method according to claim 11 , wherein access to a grouped plurality of data objects is granted on an all-or-nothing basis. 20. A computer program product comprising: a non-transitory computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising: computer readable program code configured to annotate at least one data object utilizing at least one transactional tag, the at least one transactional tag being configured to indicate a status of an associated data object, wherein the status indicates the accessibility of the at least one data object; the at least one transactional tag further being associated with one or more data structures configured to support operation of a transactional memory process; computer readable program code configured to process at least one database transaction using the at least one data object utilizing a transactional memory process, wherein access to the at least one data object is determined based on the status of the at least one data object, wherein to process comprises updating the transactional tag of the at least one data object to reserve access privilege of the at least one data object and setting access to the at least one data object as lock free, wherein the access privilege comprises a right to attempt access and operation of the at least one data object; computer readable program code configured to update the status of at least one data object, having a status of uncommitted, responsive to an attempted access of the at least one uncommitted data object by the at least one database transaction having reserved access to the at least one data obje
Physics · mapped topic
Transactional memory (G06F9/528 takes precedence) · CPC title
Optimistic concurrency control · CPC title
Concurrency control (transaction processing G06F9/466) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.