Zdenek Kabelac 0cadfdd69d tests: try running tests over ramdisk ... Currently usage of loop device over backend file in ramdisk (tmpfs) is actually causing unnecassary memory consution, since just reading such loop device is causing RAM provisioning. This patch add another possible way how to use ramdisk directly through 'brd' device when possible (and allowed). This however has it's limitation as well - brd does not support TRIM, so the only way how to erase is to remove brd module ?? Alse there is 4K sector size limitation imposed by ramdisk. Anyway - for some mirror test that were using large amount of disk space (tens of MB) this brings noticable speed boost. (But could be worth to solve the slowness of loop in kernel?) To prevent using 'brd' for testing set LVM_TEST_PREFER_BRD=0 like this: make check_local LVM_TEST_PREFER_BRD=0		2018-05-12 17:48:31 +02:00
..
api	test: D-Bus test_nesting requires filter	2017-11-09 11:57:59 +01:00
dbus	test: D-Bus test_nesting requires filter	2017-11-09 11:57:59 +01:00
lib	tests: try running tests over ramdisk	2018-05-12 17:48:31 +02:00
shell	tests: crypt test cannot run on ramdisk	2018-05-12 17:48:31 +02:00
unit	radix-tree: fix a function decl	2018-05-11 11:40:47 +01:00
.gitignore	test: add results/ to .gitignore	2016-12-10 18:00:25 +00:00
Makefile.in	tests: try running tests over ramdisk	2018-05-12 17:48:31 +02:00