[blobfs] Create BufferedOperation type
This allows clients to easily distinguish between an "UnbufferedOperation" (not yet in a buffer registered with the block device) and a "BufferedOperation", which can directly be transmitted to storage via "FlushWriteRequests". This change makes each operation self-describing, which makes it easier to operate on collections of "BufferedOperation" objects that might be acting on distinct objects (e.g., the Journal buffer vs the data writeback buffer). Change-Id: I98811f6e3a256f79fe83bd7e2ec13b717a38c3c5
Showing
- zircon/system/ulib/blobfs/include/blobfs/operation.h 14 additions, 2 deletionszircon/system/ulib/blobfs/include/blobfs/operation.h
- zircon/system/ulib/blobfs/include/blobfs/ring-buffer.h 4 additions, 4 deletionszircon/system/ulib/blobfs/include/blobfs/ring-buffer.h
- zircon/system/ulib/blobfs/include/blobfs/writeback.h 2 additions, 2 deletionszircon/system/ulib/blobfs/include/blobfs/writeback.h
- zircon/system/ulib/blobfs/ring-buffer.cpp 17 additions, 15 deletionszircon/system/ulib/blobfs/ring-buffer.cpp
- zircon/system/ulib/blobfs/test/ring-buffer-test.cpp 27 additions, 27 deletionszircon/system/ulib/blobfs/test/ring-buffer-test.cpp
- zircon/system/ulib/blobfs/test/writeback-test.cpp 24 additions, 12 deletionszircon/system/ulib/blobfs/test/writeback-test.cpp
- zircon/system/ulib/blobfs/writeback.cpp 5 additions, 6 deletionszircon/system/ulib/blobfs/writeback.cpp
Loading
Please register or sign in to comment