76acefd831
Since OCF doesn't use core and cache ids anymore adapter has to track occupied ids on its own. After loading cache, ids of all loaded cores should be marked as occupied, otherwise adding new core without explicit specifying core id will fail. Signed-off-by: Michal Mielewczyk <michal.mielewczyk@intel.com> |
||
|---|---|---|
| casadm | ||
| configure.d | ||
| modules | ||
| ocf@43e8905456 | ||
| test | ||
| utils | ||
| .gitignore | ||
| .gitmodules | ||
| .pep8speaks.yml | ||
| 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.
Getting Started
To quickly install and deploy Open CAS Linux in your system please follow the instructions available here.
Guide
The complete documentation for Open CAS Linux is available in the Open CAS Linux Administration Guide available here.
Security
To report a potential security vulnerability please follow the instructions here.