From 695719b29a6311a56faae0c6ed3c985b7a75add0 Mon Sep 17 00:00:00 2001 From: Alexander Larsson Date: Sun, 9 Feb 2014 07:25:34 +0100 Subject: [PATCH] devmapper: Enable skip_block_zeroing This makes the device mapper not zero out blocks allocated on the thinp device. This is safe in our use case, as we access the device via a filesystem that doesn't leak any uninitialized data to userspace. This partially helps with https://github.com/dotcloud/docker/issues/3280 and should generally improve preformance on the devicemapper backend. Docker-DCO-1.1-Signed-off-by: Alexander Larsson (github: alexlarsson) --- graphdriver/devmapper/devmapper.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/graphdriver/devmapper/devmapper.go b/graphdriver/devmapper/devmapper.go index 7f83a09df9..7317118dcf 100644 --- a/graphdriver/devmapper/devmapper.go +++ b/graphdriver/devmapper/devmapper.go @@ -324,7 +324,7 @@ func createPool(poolName string, dataFile, metadataFile *osFile) error { return fmt.Errorf("Can't get data size") } - params := metadataFile.Name() + " " + dataFile.Name() + " 128 32768" + params := metadataFile.Name() + " " + dataFile.Name() + " 128 32768 1 skip_block_zeroing" if err := task.AddTarget(0, size/512, "thin-pool", params); err != nil { return fmt.Errorf("Can't add target") }