Back out dirty reference tracking, as the design was flawed.
authorMichael Vrable <mvrable@cs.ucsd.edu>
Fri, 20 Aug 2010 20:51:31 +0000 (13:51 -0700)
committerMichael Vrable <mvrable@cs.ucsd.edu>
Fri, 20 Aug 2010 20:51:31 +0000 (13:51 -0700)
commit9b1a8397b18ba54e6ad6cc306e1baaecda6fe1fe
tree48679a1dc81c75bd9cdf50dc077b3518933aa3e4
parentef355dcfecf0dad2d95ff5fb3d847f1bf8b9ebe5
Back out dirty reference tracking, as the design was flawed.

Objects can be written to the journal but not to the cloud--for example, if
a data block is written to the journal but overwritten before the file is
flushed to the cloud.  This write-combining is good, but the old code for
tracking when a journal segment could be reclaimed couldn't handle this.

So, back out that dirty reference tracking code, in preparation for
replacing it with another approach.
bluesky/bluesky-private.h
bluesky/cloudlog.c
bluesky/debug.c
bluesky/log.c