Lines Matching refs:writes

12 designed to avoid random writes at all costs; it fills up an erase block
19 writes as completed until they're on stable storage).
21 Writeback caching can use most of the cache for buffering writes - writing
118  - For writethrough writes, if the write to the cache errors we just switch to
122  - For writeback writes, we currently pass that error back up to the
177    The default is 2000 us (2 milliseconds) for reads, and 20000 for writes.
193    Solution: warm the cache by doing writes, or use the testing branch (there's
287   Amount of IO (both reads and writes) that has bypassed the cache
353   Journal writes will delay for up to this many milliseconds, unless a cache
405   Minimum granularity of writes - should match hardware sector size.
408   Sum of all btree writes, in (kilo/mega/giga) bytes
434   Sum of all non data writes (btree writes and all other metadata).