US 11,892,949 B2
Reducing cache transfer overhead in a system
Christian Zoellin, Bad Urach (DE); Christian Jacobi, West Park, NY (US); Chung-Lung K. Shum, Wappinger Falls, NY (US); Martin Recktenwald, Schoenaich (DE); Anthony Saporito, Highland, NY (US); and Aaron Tsai, Hyde Park, NY (US)
Assigned to International Business Machines Corporation, Armonk, NY (US)
Filed by INTERNATIONAL BUSINESS MACHINES CORPORATION, Armonk, NY (US)
Filed on Jan. 13, 2023, as Appl. No. 18/154,204.
Application 18/154,204 is a continuation of application No. 17/226,592, filed on Apr. 9, 2021, granted, now 11,586,542.
Application 17/226,592 is a continuation of application No. 16/745,411, filed on Jan. 17, 2020, granted, now 11,010,298.
Application 16/745,411 is a continuation of application No. 15/625,097, filed on Jun. 16, 2017, granted, now 10,585,800, issued on Mar. 10, 2020.
Prior Publication US 2023/0153244 A1, May 18, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 12/0817 (2016.01); G06F 12/0831 (2016.01); G06F 12/0842 (2016.01)
CPC G06F 12/0828 (2013.01) [G06F 12/0822 (2013.01); G06F 12/0833 (2013.01); G06F 12/0842 (2013.01); G06F 2212/1024 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method for managing data object contention in a computing system, the method comprising:
receiving an intervention notification associated with a first request to obtain a first copy of a first data object, the first request associated with a first computing application, among a plurality of computing applications included in the computing system;
recording, based at least in part on receiving the intervention notification, a first hot object status indicating that the first data object is a potential hot data object;
suppressing, based at least in part on the recorded first hot object status indicating that the first data object is a potential hot data object, an action associated with performing an operation associated with the first data object;
receiving the first request;
determining that the first request is associated with a read-only use of the first data object;
determining that a second computing application, among the plurality of computing applications, has the first copy of the first data object;
determining that a usage status of the first copy of the first data object comprises a read-only status, and demoting the usage status from read/write status to the read-only status; and
communicating, based at least in part on the first request associated with the read-only use of the first copy of the first data object and the first copy of the first data object having the read-only status, a notification that the first request did not cause an intervention associated with the first copy of the first data object.