mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-21 13:34:40 +03:00
3a7aeebf7d
If we plan to use dm throttling for mirror targets - we actually have to check whether kernel runs with CONFIG_HZ_1000 - if it does not the whole idea of throttling is actually not working in the testsuite as within a single 'tick' with HZ 100 way too much date is being moved on any modern hardware - and since there is no plan to change this in kernel - we simply avoid using throttling on such kernel and test needs to work differently - either ignore results or use much larger mirror sizes... |
||
---|---|---|
.. | ||
aux.sh | ||
brick-shelltest.h | ||
check.sh | ||
dmsecuretest.c | ||
flavour-ndev-cluster-lvmpolld.sh | ||
flavour-ndev-cluster.sh | ||
flavour-ndev-devicesfile.sh | ||
flavour-ndev-lvmpolld.sh | ||
flavour-ndev-vanilla.sh | ||
flavour-udev-cluster-lvmpolld.sh | ||
flavour-udev-cluster.sh | ||
flavour-udev-lvmlockd-dlm.sh | ||
flavour-udev-lvmlockd-idm.sh | ||
flavour-udev-lvmlockd-sanlock.sh | ||
flavour-udev-lvmlockd-test.sh | ||
flavour-udev-lvmpolld.sh | ||
flavour-udev-vanilla.sh | ||
get.sh | ||
harness.c | ||
idm_inject_failure.c | ||
inittest.sh | ||
lvm_vdo_wrapper.sh | ||
lvm-wrapper.sh | ||
mke2fs.conf | ||
not.c | ||
runner.cpp | ||
test-corosync-conf | ||
test-dlm-conf | ||
test-sanlock-conf | ||
utils.sh |