Re: Kernel panic with current bcache-3.2 branch.

There also seems to have been pretty severe performance regressions in
cache bypassed sequential I/O.
The newer code barely does 70mb/s sequential writes when
sequential_cuttoff is set to 4M however it does around 300mb/s when
set to 0 (no bypass) with dd and 1M block size.
When using the older codebase the cache bypass is actually slightly
faster than going to cache at around 360mb/s but this is still much
slower than the underlying block devices (as previously discussed).

Joseph.

-- 
CTO | Orion Virtualisation Solutions | www.orionvm.com.au
Phone: 1300 56 99 52 | Mobile: 0428 754 846