Toronto, Canada

Dale J Hagen

This inventor holds 1 USPTO granted patent. Top assignee: International Business Machines Corporation. Active years: 2005.

IDiyas Innovation Intelligence. (2026). Inventor Profile: Dale J Hagen. Retrieved from https://idiyas.com/inventor/dale-j-hagen

Data source: USPTO (United States Patent and Trademark Office) public patent records. Weekly synchronization. How IDiyas builds this profile

Calculating rank

Average Co-Inventor Count = 6.0

ph-index = 1

Forward Citations = 2(Granted Patents)


Company Filing History:


Years Active: 2005

Loading Chart...
1 patent (USPTO):Explore Patents

Title: Dale J. Hagen and Adaptive Spin Latches.

Introduction

Dale J. Hagen is an inventor associated with Toronto, Canada, and International Business Machines Corporation. His work includes an invention for managing access to shared resources in multiprocessor computer systems.

Latest Patents

Hagen is credited with 1 patent, titled “Adaptive Spin Latches.” The patent describes a system that regulates how agents access a resource in a multiprocessor computer. It uses a run queue to track agents that are active, a spin latch module to place agents into sleep mode for periods based on the number of agents waiting, and a wait queue to track sleeping agents. The approach is designed to coordinate access while managing contention among agents.

Career Highlights

Hagen’s listed patent is associated with International Business Machines Corporation, commonly known as IBM. The invention addresses synchronization and resource-access challenges in multiprocessor computing.

Collaborations

Hagen’s listed coworkers include Mark Francis Wilding and Dominique Jeremy Evans.

Conclusion

Dale J. Hagen’s patent on adaptive spin latches reflects work on coordinating resource access and managing waiting agents in multiprocessor systems.

Profile summary based on public USPTO records.
Data Sources: USPTO Patent Grant XML, Patent Center, EPO & CIPO • Normalized by IDiyas Innovation Graph. Methodology & provenance architecturePlease report any incorrect information to [email protected]
Loading…