diff src/org/dancres/blitz/arc/sync_cond.txt @ 0:3dc0c5604566

Initial checkin of blitz 2.0 fcs - no installer yet.
author Dan Creswell <dan.creswell@gmail.com>
date Sat, 21 Mar 2009 11:00:06 +0000
parents
children
line wrap: on
line diff
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/src/org/dancres/blitz/arc/sync_cond.txt	Sat Mar 21 11:00:06 2009 +0000
@@ -0,0 +1,14 @@
+Could we schedule I/O in such a fashion as to be outside of locks involved in
+a deadlock situation?
+
+Cache lock = sync() lock in ArcCache.
+CBD lock is the individual mutex of a CBD.
+
+What are the conditions for achieving this?
+
+We must have done all cache list modifications before releasing the cache lock.
+   - This ensures another thread doesn't, for example, recover a CBD with one
+   id which, in fact, is being "renamed" to another id.
+   - We must also do this to protect the state of the various lists which
+   constitute a chunk of the cache state.  Question, is the state of a CDB's
+   content part of the cache state?