ColoredLock synchronization object, allowing flow specific policy of lock canceling
Aspects for operating a computer system include a colored lock synchronization object allowing flow specific policy of lock canceling. An extended lock object Application Programming Interface (API) including a color attribute is utilized. A color attribute is passed to the extended lock API, whereby the color attribute reflects a type of flow or thread that called a colored lock object. Selective termination of requests waiting on a colored lock object can be utilized to prevent a potential deadlock condition.
1. A method of allowing a flow specific policy of lock canceling, the method comprising:
receiving a request for a lock object, the request received at a storage system from a calling thread, the request including a color attribute that indicates a type of flow associated with the calling thread;
passing the request with the color attribute to an extended lock object application programming interface (API) at the storage system; and
performing, at the storage system, selective termination of requests that are waiting on the lock object, the selective termination based on the color attribute, and the requests including the request for the lock object;
wherein the extended lock object API includes calls comprising:
a lock call including the lock object and the color attribute;
an unlock call including the lock object;
a cancel lock by color call including the lock object and a colors mask attribute; and
a clear color mask call including the lock object.
2. The method of claim 1 further comprising:
upon determining the lock object is free and that the lock object can be presently completed, ignoring the color attribute in performing an operation on the lock object.
3. The method of claim 1 further comprising:
upon determining that the lock object is locked, queuing the calling thread in a waiting queue of the lock object along with the color attribute.
4. The method of claim 3 further comprising:
returning, via the extended lock object API, a lock acquired result if the lock object is acquired, or an aborted result if the calling thread in the waiting queue is cancelled by the cancel lock by color call.
5. The method of claim 4 wherein:
the cancel lock by color call prevents a new attempt to get the lock object having a color matching colors mask attribute to be rejected and returns an aborted result to the calling thread by the lock object; and
wherein the cancel lock by color call results in a scanning of the waiting queue, and each entry in the waiting queue that has the color matching colors mask attribute is removed from the waiting queue and an aborted result is returned to the calling thread by the corresponding lock object.
6. The method of claim 1 wherein the clear color mask call clears a colors mask defined by a previously issued cancel lock by color call and allows standard operation of the lock object.
7. A system comprising:
a processor; and
memory storing computer program code that when executed on the processor causes the processor to operate a storage system, the storage system operable to perform the operations of:
receiving a request for a lock object, the request received at a storage system from a calling thread, the request including a color attribute that indicates a type of flow associated with the calling thread;
passing the request with the color attribute to an extended lock object application programming interface (API) at the storage system; and
performing, at the storage system, selective termination of requests that are waiting on the lock object, the selective termination based on the color attribute, and the requests including the request for the lock object;
wherein the extended lock object API includes calls comprising:
a lock call including the lock object and the color attribute;
an unlock call including the lock object;
a cancel lock by color call including the lock object and a colors mask attribute; and
a clear color mask call including the lock object attribute.
8. The system of claim 7 , wherein the operations further comprise:
upon determining the lock object is free and that the lock object can be presently completed, ignoring the color attribute in performing an operation on the lock object.
9. The system of claim 7 , further comprising:
upon determining that the lock object is locked, queuing the calling thread in a waiting queue of the lock object along with the color attribute.
10. The system of claim 9 , further comprising:
returning, via the extended lock object API a lock acquired result if the lock object is acquired, or an aborted result if the calling thread in the waiting queue is cancelled by the cancel lock by color call.
11. The system of claim 10 wherein:
the cancel lock by color call prevents a new attempt to get the lock object having a color matching colors mask attribute to be rejected and returns an aborted result to the calling thread.
12. The system of claim 10 , wherein the cancel lock by color call results in a scanning of the waiting queue, and each entry in the waiting queue that has the color matching colors mask attribute is removed from the waiting queue and an aborted result is returned to the calling thread.
13. The system of claim 7 wherein the clear color mask call clears a colors mask defined by a previously issued cancel lock by color call and allows a standard operation of the lock object.
14. A computer program product including a non-transitory computer readable storage medium having computer program code encoded thereon for allowing a flow specific policy of lock canceling that when executed on a processor of a computer causes the computer to operate a storage system, the computer program product comprising for performing operations, the operations comprising:
receiving a request for a lock object, the request received at a storage system from a calling thread, the request including a color attribute that indicates a type of flow associated with the calling thread;
passing the request with the color attribute to an extended lock object application programming interface (API) at the storage system; and
performing, at the storage system, selective termination of requests that are waiting on the lock object, the selective termination based on the color attribute, and the requests including the request for the lock object;
wherein the extended lock object API includes calls comprising:
a lock call including the lock object and the color attribute;
an unlock call including the lock object;
a cancel lock by color call including the lock object and a colors mask attribute; and
a clear color mask call including the lock object.
15. The computer program product of claim 14 wherein the operations further comprise:
upon determining the lock object is free and that the lock object can be presently completed, ignoring the color attribute in performing an operation on the lock object;
upon determining that the lock object is locked, queuing the calling thread in a waiting queue of the lock object along with the color attribute; and
returning, via the extended lock object API a lock acquired result if the lock object is acquired, or an aborted result if the calling thread in the waiting queue is cancelled by the cancel lock by color call.
16. The computer program product of claim 14 , wherein:
the cancel lock by color call prevents a new attempt to get the lock object having a color matching colors mask attribute to be rejected and returns an aborted result to the calling thread by the corresponding lock object;
the cancel lock by color call results in a scanning of the waiting queue, and each entry in the waiting queue that has the color matching colors mask attribute is removed from the waiting queue and the corresponding lock object returns an aborted result; and
the clear color mask call clears a colors mask defined by a previously issued cancel lock by color call and allows a standard operation of the lock object.