Skip to content
Snippets Groups Projects
  1. Feb 03, 1999
  2. Feb 02, 1999
  3. Feb 01, 1999
  4. Jan 31, 1999
  5. Jan 29, 1999
  6. Jan 28, 1999
  7. Jan 27, 1999
  8. Jan 26, 1999
    • Kurt Zeilenga's avatar
      LDBM/back-ldbm locking reworked! · bd6dfe33
      Kurt Zeilenga authored
      	back-ldbm was using a cache specific lock to protect non-reentrant
      	database routines from being reenterred.  This is inadequate.
      	Also, reentrant database systems calls were serialized unnecessarily.
      
      	Non-reentrant database calls must have a big_mutex.  Implemented
      	this within -lldbm itself.  library requires ldbm_initialize()
      	be called before any other ldbm call to initialize the big_mutex
      	and to do any other db specific initialization (ie: such as
      	required for DB2).
      
      The dbc_mutex, dbc_cv, & dbc_readers fileds of dbcache are history.
      The "reentrant_database" (REENTRANT_DATABASE) define is also axed.
      bd6dfe33
    • Kurt Zeilenga's avatar
      f3fb0c74
    • Kurt Zeilenga's avatar
      Hide allocate of reentrant_database cond varible and reader count · f1e934ef
      Kurt Zeilenga authored
      behind REENTRANT_DATABASE.  rename reentrant_database -> REENTRANT_DATABASE.
      When REENTRANT_DATABASE is defined, the simple lock is replaced
      with a simple reader/writer lock.  This functionality should be removed
      from back-ldbm to libldbm.
      f1e934ef
    • Kurt Zeilenga's avatar
      cache_set_state( cache, e, 0) cannot occur before lock on parent/root · 3c67248a
      Kurt Zeilenga authored
      is released.  Some other thread may have cache locked but blocking
      on parent.  Must give up parent lock before acquiring cache lock.
      3c67248a
Loading