Microsoft Technology Licensing, LLC

John Austin Rector

Eric Li

Arun Upadhyaya Kishan

Neill Michael Clift

David Bradley Probert, Jr

Genevieve Fernandes

Jonathan David Morrison

A multi-level sequence number is associated with a data provider supplying data for an object. The multi-level sequence number includes a portion that is unique to the data provider, and one or more portions that are shared by other data providers for the object. A per-object table is used to cache data supplied by each data provider for the object and the corresponding multi-level sequence number. A global table associates each data provider with the current value of its multi-level sequence number. Whenever data supplied by a data provider changes, the sequence number in the global table is updated. Cached data of the data provider is updated with current data of the data provider only if the cached value of the sequence number is found to be different from the current value of the sequence number.

Multi-level sequence number based lazy invalidation

A blocking local sense synchronization barrier is provided. The local sense variable is not processor private or global, but truly local to the synchronization barrier function. Safe deletion is provided by making sure the last operation a thread performs on a barrier is a write. Just before returning, threads increment a field that indicates the count of threads that have left the barrier. Blocking is supported such that threads spin for some interval, and when they decide to block, examine and set (if not already set) the indication of whether a thread is blocking that is to be examined by the last thread to arrive at the barrier to determine whether to set an event to release blocking threads.

Blocking local sense synchronization barrier

A system and method for identity decisions and invalidation. Modified objects (e.g., files, executables, etc.) are flagged for reevaluation. Privileges associated with the object are only persisted if the modifications are determined to be authorized (e.g., updates and patches). In one embodiment, a tagging system registers to be notified of all writes, renames, truncations, moves, deletions, or any other relevant modifications to objects. If the tagging system detects a modification operation targeting the object, it invalidates all identity decisions cached with the object. The next time the object runs, the system does not recognize the object and it is forced to reevaluate its identity. Thus, patching and other write operations are still permitted, but the system detects the changed object and reevaluates the identity.

Growing community of inventors

Redmond, WA, United States of America

John Austin Rector