ffa1f4b067
Write-only (WO) cache mode is similar to Write-back (WB), however read operations do not promote data to cache. Reads are mostly serviced by the core device, only dirty sectors are fetched from the cache. Write-only cache mode is behaving similarly to Write-back with respect to flushing dirty data. For example it is required to explicitly enable/disable flushing when changing cache mode from WO to something other than WB. Signed-off-by: Adam Rutkowski <adam.j.rutkowski@intel.com> |
||
|---|---|---|
| casadm | ||
| configure.d | ||
| modules | ||
| ocf@aeaeafb639 | ||
| test | ||
| utils | ||
| .gitignore | ||
| .gitmodules | ||
| configure | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
Open CAS Linux
Open CAS accelerates Linux applications by caching active (hot) data to a local flash device inside servers. Open CAS implements caching at the server level, utilizing local high-performance flash media as the cache drive media inside the application server as close as possible to the CPU, thus reducing storage latency as much as possible. The Open Cache Acceleration Software installs into the GNU/Linux operating system itself, as a kernel module. The nature of the integration provides a cache solution that is transparent to users and applications, and your existing storage infrastructure. No storage migration effort or application changes are required.
Open CAS is distributed on BSD-3-Clause license (see https://opensource.org/licenses/BSD-3-Clause for full license texts).
Open CAS uses Safe string library (safeclib) that is MIT licensed.
Security
To report a potential security vulnerability please follow the instructions here.