Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: Reader-writer locks (rwlocks) aim to maximize parallelism among readers, but many existing rwlocks either cause readers to contend, or significantly extend writer latency, or both. Further, some scalable rwlocks cannot cope with OS semantics like sleeping inside critical sections, preemption and conditional wait. Though truly scalable rwlocks exist, some of them cannot handle preemption, sleeping inside critical sections, or other important functions required inside OS kernels.  describes a new rwlock called the passive reader-writer lock (prwlock) that provides scalable read-side performance as ll as small writer latency for TSO architectures. The key of prwlock is a version-based consensus protocol beten multiple non-communicating readers and a pending writer. Prwlock leverages bounded staleness of memory consistency to avoid atomic instructions and memory barriers in readers' common paths, and uses message-passing (e.g., IPI) for straggling readers so that writer lock acquisition latency can be bounded. Evaluation on a 64-core machine shows that prwlock significantly boosts the performance of the Linux virtual memory subsystem, a concurrent hashtable and an in-memory database.
['Ran Liu', 'Heng Zhang', 'Haibo Chen']
I am writing a research paper on a idea Scalable read-mostly synchronization using passive reader-writer locks
[{"from": "human", "value": "I am writing a research paper on a idea Scalable read-mostly synchronization using passive reader-writer locks"}, {"from": "gpt", "value": "Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: Reader-writer locks (rwlocks) aim to maximize parallelism among readers, but many existing rwlocks either cause readers to contend, or significantly extend writer latency, or both. Further, some scalable rwlocks cannot cope with OS semantics like sleeping inside critical sections, preemption and conditional wait. Though truly scalable rwlocks exist, some of them cannot handle preemption, sleeping inside critical sections, or other important functions required inside OS kernels.  describes a new rwlock called the passive reader-writer lock (prwlock) that provides scalable read-side performance as ll as small writer latency for TSO architectures. The key of prwlock is a version-based consensus protocol beten multiple non-communicating readers and a pending writer. Prwlock leverages bounded staleness of memory consistency to avoid atomic instructions and memory barriers in readers' common paths, and uses message-passing (e.g., IPI) for straggling readers so that writer lock acquisition latency can be bounded. Evaluation on a 64-core machine shows that prwlock significantly boosts the performance of the Linux virtual memory subsystem, a concurrent hashtable and an in-memory database."}]