to `print_slow_atomic_cache_start_info` after removing check from lower
function `_check_cache_device`.
Signed-off-by: Slawomir Jankowski <slawomir.jankowski@intel.com>
Not every usage of `set_device_path()` needs to print message.
Sometimes it's internal operation and can contain misleading info.
Signed-off-by: Slawomir Jankowski <slawomir.jankowski@intel.com>
Check if path passed to core adding or cache starting is by-id link
otherwise do not allow to use it except it is exported object's path.
Do not resolve device's by-id path during core addition or cache starting.
Signed-off-by: Slawomir Jankowski <slawomir.jankowski@intel.com>
This fixes startup bug when core was added to core pool by md-name*
symlink, but cache metadata contained md-uuid* path, which led to
incomplete configuration
Signed-off-by: Robert Baldyga <robert.baldyga@intel.com>
Since there is no kernel-kernel api available to communicate
with nvme driver it is more convenient to use some nvme-dedicated
software (e.g. nvme-cli) to manage nvme devices.
It is even not possible to format nvme device with CAS using current
implementation on newest kernels.
Signed-off-by: Michal Rakowski <michal.rakowski@intel.com>
Signed-off-by: Michal Mielewczyk <michal.mielewczyk@intel.com>
Purge invalidates all cache lines which belongs to given core. It is very
usefull feature for tests.
Calling purge is possbile with casadm `--script` swtich.
Signed-off-by: Michal Mielewczyk <michal.mielewczyk@intel.com>
Purge invalidates all cache lines. It is very usefull feature for tests.
Calling purge is possbile with casadm `--script` swtich.
Signed-off-by: Michal Mielewczyk <michal.mielewczyk@intel.com>
The functionality of displaying flush progress in caches list
was removed. Updating casadm user message to reflect this.
Signed-off-by: Adam Rutkowski <adam.j.rutkowski@intel.com>
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>
