Lines Matching refs:it

1 Say you've got a big slow raid 6, and an X-25E or three. Wouldn't it be
9 It's designed around the performance characteristics of SSDs - it only allocates
10 in erase block sized buckets, and it uses a hybrid btree/log to track cached
12 designed to avoid random writes at all costs; it fills up an erase block
13 sequentially, then issues a discard before reusing it.
17 great lengths to protect your data - it reliably handles unclean shutdown. (It
26 to caching large sequential IO. Bcache detects sequential IO and skips it;
27 it also keeps a rolling average of the IO sizes per task, and as long as the
28 average is above the cutoff it will skip all IO from that task - instead of
32 In the event of a data IO error on the flash it will try to recover by reading
35 in the cache it first disables writeback caching and waits for all dirty data
56 now format it and use it as normal. But the first time using a new bcache
57 device, it'll be running in passthrough mode until you attach it to a cache.
103 The backing device will still use that cache set if it shows up in the future,
111 affecting normal operation; if it sees too many errors (the threshold is
112 configurable, and defaults to 0) it shuts down the cache device and switches all
123    filesystem/userspace. This could be improved - we could retry it as a write
127    writeback mode). It currently doesn't do anything intelligent if it fails to
157    To set it back to the default (4 mb), do
165    you want to avoid being bottlenecked by the SSD and having it slow everything
169    throttles traffic if the latency exceeds a threshold (it does this by
186    In practice this isn't an issue because as soon as a write comes along it'll
213   cache, it will be flushed first.
224   1M, it will round cache miss reads up to that size, but without overlapping
229   it's in passthrough mode or caching).
232   A sequential IO will bypass the cache once it passes this threshold; the
234   it isn't all done at once.
261   When dirty data is written to the cache and it previously did not contain
277   still be added to the cache until it is mostly full; only meant for
369   present it will disable writeback caching and wait for it to be flushed.
417   Boolean; if on a discard/TRIM will be issued to each bucket before it is
427   the SSD's garbage collection easier by effectively giving it more reserved