Efficient garbage collection and exception handling in a hardware accelerated transactional memory system
First Claim
1. In a computing environment comprising a hardware assisted transaction system, a method of writing to a card table in a generational garbage collection system that gives preference to performing garbage collection activities on newer generation generational objects, and where writing to the card table marks older generation generational objects that are updated with references pointing to newer generation generational objects so that references by the older generation generational objects can be given preference in garbage collection activities, the method comprising:
- beginning a hardware assisted transaction to cause reads and writes to be buffered and monitored to prevent conflicting reads and writes, using an isolated cache memory structure;
determining, while the transaction is running, that a write entry needs to be made to a card table to keep track of a reference from an older generation generational object in a generational garbage collection system to a newer generation generational object in the generational garbage collection system; and
as a result of determining that a write entry needs to be made to a card table performing a write to an entry in the card table outside of the transaction, such that the entry is not added to the transaction'"'"'s write set and such that the write does not establish read or write monitoring on the entry, and such that the reference from the older generation generational object to the newer generation generational object in the card table remains even if the transaction is subsequently rolled back, thus causing garbage collection operations to be performed using the reference to the newer generational object irrespective of whether the reference is valid as a result of the transaction having committed or invalid as a result of the transaction having been rolled back.
3 Assignments
0 Petitions
Accused Products
Abstract
Handling garbage collection and exceptions in hardware assisted transactions. Embodiments are practiced in a computing environment including a hardware assisted transaction system. Embodiments includes acts for writing to a card table outside of a transaction; handling garbage collection compaction occurring when a hardware transaction is active by using a common global variable and instructing one or more agents to write to the common global variable any time an operation is performed which may change an object'"'"'s virtual address; acts for managing a thread-local allocation context; acts for handling exceptions while in a hardware assisted transaction. A method includes beginning a hardware assisted transaction, raising an exception while in the hardware assisted transaction, including creating an exception object, determining that the transaction should be rolled back, and as a result of determining that the transaction should be rolled back, marshaling the exception object out of the hardware assisted transaction.
-
Citations
18 Claims
-
1. In a computing environment comprising a hardware assisted transaction system, a method of writing to a card table in a generational garbage collection system that gives preference to performing garbage collection activities on newer generation generational objects, and where writing to the card table marks older generation generational objects that are updated with references pointing to newer generation generational objects so that references by the older generation generational objects can be given preference in garbage collection activities, the method comprising:
-
beginning a hardware assisted transaction to cause reads and writes to be buffered and monitored to prevent conflicting reads and writes, using an isolated cache memory structure; determining, while the transaction is running, that a write entry needs to be made to a card table to keep track of a reference from an older generation generational object in a generational garbage collection system to a newer generation generational object in the generational garbage collection system; and as a result of determining that a write entry needs to be made to a card table performing a write to an entry in the card table outside of the transaction, such that the entry is not added to the transaction'"'"'s write set and such that the write does not establish read or write monitoring on the entry, and such that the reference from the older generation generational object to the newer generation generational object in the card table remains even if the transaction is subsequently rolled back, thus causing garbage collection operations to be performed using the reference to the newer generational object irrespective of whether the reference is valid as a result of the transaction having committed or invalid as a result of the transaction having been rolled back. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. In a computing environment comprising a hardware assisted transaction system, a system for writing to a card table in a generational garbage collection system that gives preference to performing garbage collection activities on newer generation generational objects, and where writing to the card table marks older generation generational objects that are updated with references pointing to newer generation generational objects so that references by the older generation generational objects can be given preference in garbage collection activities, the system comprising:
-
one or more processors; and one or more computer readable media, wherein the one or more computer readable media comprise computer executable instructions that when executed by at least one of the one or more processors cause at least one of the one or more processors to perform the following; beginning a hardware assisted transaction to cause reads and writes to be buffered and monitored to prevent conflicting reads and writes, using an isolated cache memory structure; determining, while the transaction is running, that a write entry needs to be made to a card table to keep track of a reference from an older generation generational object in a generational garbage collection system to a newer generation generational object in the generational garbage collection system; and as a result of determining that a write entry needs to be made to a card table performing a write to an entry in the card table outside of the transaction, such that the entry is not added to the transaction'"'"'s write set and such that the write does not establish read or write monitoring on the entry, and such that the reference from the older generation generational object to the newer generation generational object in the card table remains even if the transaction is subsequently rolled back, thus causing garbage collection operations to be performed using the reference to the newer generational object irrespective of whether the reference is valid as a result of the transaction having committed or invalid as a result of the transaction having been rolled back. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
13. One or more computer readable storage media, wherein the one or more computer readable storage media comprise computer executable instructions that when executed by at least one of the one or more processors cause at least one of the one or more processors to perform the following:
-
beginning a hardware assisted transaction to cause reads and writes to be buffered and monitored to prevent conflicting reads and writes, using an isolated cache memory structure; determining, while the transaction is running, that a write entry needs to be made to a card table to keep track of a reference from an older generation generational object in a generational garbage collection system to a newer generation generational object in the generational garbage collection system; and as a result of determining that a write entry needs to be made to a card table performing a write to an entry in the card table outside of the transaction, such that the entry is not added to the transaction'"'"'s write set and such that the write does not establish read or write monitoring on the entry, and such that the reference from the older generation generational object to the newer generation generational object in the card table remains even if the transaction is subsequently rolled back, thus causing garbage collection operations to be performed using the reference to the newer generational object irrespective of whether the reference is valid as a result of the transaction having committed or invalid as a result of the transaction having been rolled back. - View Dependent Claims (14, 15, 16, 17, 18)
-
Specification