Go to file
Adam Rutkowski cfaf0d279f Abort cache deinit in case of ocf stop fatal error
We should only proceed with deinitialization in case of cache
write error, not just any error.

Signed-off-by: Adam Rutkowski <adam.j.rutkowski@intel.com>
2019-04-10 14:36:07 -04:00
casadm Initial commit 2019-03-29 08:45:50 +01:00
modules Abort cache deinit in case of ocf stop fatal error 2019-04-10 14:36:07 -04:00
ocf@0192f4070d Pick up latest OCF 2019-04-02 14:37:56 -04:00
utils Initial commit 2019-03-29 08:45:50 +01:00
.gitignore Add .gitignore 2019-04-04 17:55:40 -04:00
.gitmodules Initial commit 2019-03-29 08:45:50 +01:00
LICENSE Add LICENSE file 2019-03-29 09:45:21 +01:00
Makefile Initial commit 2019-03-29 08:45:50 +01:00
README.md Add LICENSE file 2019-03-29 09:45:21 +01:00

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.