Lines Matching full:blocks

27 		start writeback when the number of used blocks reach this
30 		stop writeback when the number of used blocks drops below
33 		limit the number of blocks that are in flight during
37 		when the application writes this amount of blocks without
38 		issuing the FLUSH request, the blocks are automatically
58 		new writes (however, writes to already cached blocks are
63 		blocks drops to zero, userspace can unload the
80 2. the number of blocks
81 3. the number of free blocks
82 4. the number of blocks under writeback
83 5. the number of read blocks
84 6. the number of read blocks that hit the cache
85 7. the number of write blocks
86 8. the number of write blocks that hit uncommitted block
87 9. the number of write blocks that hit committed block
88 10. the number of write blocks that bypass the cache
89 11. the number of write blocks that are allocated in the cache
92 14. the number of discarded blocks