eeda1f3f0f
Reformat function that calculates how long cache/core is dirty Update `dirty_for` types in functional tests Values stored in info structs fields (both in cache and core structs) are unsigned 64-bits ints but `dirty_for`s were unsigned 32-bits ints. Use existing function to transform returned value to seconds. Replace seconds stored in metadata with seconds. Replacement was done if old value of replaced field was equal to zero. Acquiring monotonic high precission timestamp is potentially slow and it makes sense to compare the field's value to zero before calling atomic function. Signed-off-by: Slawomir Jankowski <slawomir.jankowski@intel.com> |
||
|---|---|---|
| doc | ||
| env/posix | ||
| example/simple | ||
| inc | ||
| src | ||
| tests | ||
| .pep8speaks.yml | ||
| codecov.yml | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
Open CAS Framework
Open CAS Framework (OCF) is high performance block storage caching meta-library written in C. It's entirely platform and system independent, accessing system API through user provided environment wrappers layer. OCF tightly integrates with the rest of software stack, providing flawless, high performance, low latency caching utility.
In this readme:
- Documentation
- Source Code
- Deployment
- Examples
- Unit Tests
- Build Test
- Functional Tests
- Contributing
- Security
Documentation
OCF documentation is available on GitHub Pages. Doxygen API documentation is available here.
Source Code
Source code is available in the official OCF GitHub repository:
git clone https://github.com/Open-CAS/ocf.git
cd ocf
Deployment
OCF doesn't compile as separate library. It's designed to be included into another software stack. For this purpose OCF provides Makefile with two useful targets for deploying its source into target directories. Assuming OCFDIR is OCF directory, and SRCDIR and INCDIR are respectively your source and include directories, use following commands to deploy OCF into your project:
make -C $OCFDIR src O=$SRCDIR
make -C $OCFDIR inc O=$INCDIR
By default this will not copy OCF source files but create symbolic links to them, to avoid source duplication and allow for easy OCF code modification. If you prefer to copy OCF source files (e.g. you don't want to distribute whole OCF repository as your submodule) you can use following commands:
make -C $OCFDIR src O=$SRCDIR CMD=cp
make -C $OCFDIR inc O=$INCDIR CMD=cp
Examples
OCF is shipped with examples, which are complete, compillable and working programs, containing lot of comments that explain basics of caching. They are great starting point for everyone who wants to start working with OCF.
Examples can be found in directory example/.
Each example contains Makefile which can be used to compile it.
Unit Tests
OCF is shipped with dedicated unit test framework based on Cmocka.
To run unit tests you need to install following packages:
- Cmake (>= 3.8.1)
- Cmocka (>= 1.1.1)
- ctags (>= 5.8)
To run unit tests use following command:
./tests/unit/framework/run_unit_tests.py
Build Test
OCF repository contains basic build test. It uses default POSIX environment. To run this test, use following commands:
cd tests/build/
make
Functional Tests
OCF repository contains dedicated functional test framework written in python and executed via pytest. With the use of ctypes it is possible to call, wrap ocf functions and use C compatible data types.
To run functional tests you need to install the following:
- python3 (>=3.6.7)
- pytest (Install with
pip3 install pytest)
To run all functional tests (in compliance with the configuration file) compile using makefile located in ./tests/functional/Makefile and then use the following command:
pytest
Contributing
Feel like making OCF better? Don't hesitate to submit a pull request!
You can find more information about our contribution process
here.
In case of any questions feel free to contact maintainer.
Security
To report a potential security vulnerability please follow the instructions here