Go to file
Adam Rutkowski 79eb92cd9a Implement secure alloc/free using vmalloc/vfree
In kernel there is no point in mlocking and zeroring memory
before freeing.

Signed-off-by: Adam Rutkowski <adam.j.rutkowski@intel.com>
2019-04-18 18:04:57 -04:00
casadm Prevent cache mode to be truncated in case of 'Unknown' mode. 2019-04-11 08:50:12 -04:00
modules Implement secure alloc/free using vmalloc/vfree 2019-04-18 18:04:57 -04:00
ocf@0b098ddb80 Update OCF 2019-04-18 18:04:56 -04:00
test/smoke_test Added framework for smoke tests and few basic tests. 2019-04-15 11:51:19 -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.