This project is read-only.

Don't favor write locks so much


The current implementation has a locking policy which favors write locks more. It doesn't have to be completely equal between supporting write locks and read locks, but it would be nice if it supported read locks more so write locks don't starve read locks from performing as often as they should.


TamusJRoyce wrote Oct 7, 2010 at 8:32 AM

I believe I mean unbias lock ordering. By that I mean that the number of threads that start reading go first. Then if a write comes in, it is done after those previous reads finish. But if any read locks come after this write lock is done (in which it is waiting on reading to finish), those reading threads are held off until the write finishes.

This is my next priority.

TamusJRoyce wrote Oct 20, 2010 at 1:06 PM

On hold from being my next priority. Read-write spinlocks seem more important. I may get distracted with policy based locking before this, too.

wrote Feb 12, 2013 at 10:43 PM