Lines Matching refs:block

10 storage as traditional block devices. The block drivers for persistent memory
13 using stored energy in capacitors to complete in-flight block writes, or perhaps
15 progress, and we experience a power failure, the block will contain a mix of old
20 being torn can continue to do so. The BTT manifests itself as a stacked block
41 |               |   |   | Arena info block |
66                         | Info block copy  |
79 block. Each map entry is 32 bits. The two most significant bits are special
80 flags, and the remaining form the internal block number.
100 Premap ABA    : The block offset into an arena, which was decided upon by range
102 Postmap ABA   : The block number in the "Data Blocks" area obtained after
111 worth of blocks that this arena contributes, this block is at 256G. Thus, the
112 premap ABA is 256G. We now refer to the map, and find out the mapping for block
113 'X' (256G) points to block 'Y', say '64'. Thus the postmap ABA is 64.
120 i.e. Every write goes to a "free" block. A running list of free blocks is
126 	  free block.
162 writes. We can hit a condition where the writer thread grabs a free block to do
164 the reader consulted a map entry, and started reading the corresponding block. A
167 internal, postmap block that the reader is (still) reading has been inserted
169 grab this free block, and start writing to it, causing the reader to read
174 read is complete. Every writer thread, after grabbing a free block, checks the
175 RTT for its presence. If the postmap free block is in the RTT, it waits till the
222 7.  Read data from this block
230 3.  Use lane to index into in-memory free list and obtain a new block, next flog
232 4.  Scan the RTT to check if free block is present, and spin/wait if it is.
233 5.  Write data to this free block
248 - Info block checksum does not match (and recovering from the copy also fails)
256 only state using a flag in the info block.
262 Any block driver that supports byte granularity IO to the storage may register
276 The BTT 'disk' appears as a stacked block device that grabs the underlying block