summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLinux Build Service Account <lnxbuild@localhost>2018-06-28 02:34:28 -0700
committerGerrit - the friendly Code Review server <code-review@localhost>2018-06-28 02:34:27 -0700
commit14efecefa760800fa4d6974054b52e3e7ca91d3f (patch)
treee1d877bcca0ed1ab28fc6f6f897fafb964953545 /Documentation
parent66c519deb658ad6c8395d681bc6123a8098a7752 (diff)
parentf9cff13b5d3e04e897a495168da90933b503a6cc (diff)
Merge "Merge android-4.4.135 (c9d74f2) into msm-4.4"
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/device-mapper/thin-provisioning.txt8
1 files changed, 5 insertions, 3 deletions
diff --git a/Documentation/device-mapper/thin-provisioning.txt b/Documentation/device-mapper/thin-provisioning.txt
index 1699a55b7b70..ef639960b272 100644
--- a/Documentation/device-mapper/thin-provisioning.txt
+++ b/Documentation/device-mapper/thin-provisioning.txt
@@ -112,9 +112,11 @@ $low_water_mark is expressed in blocks of size $data_block_size. If
free space on the data device drops below this level then a dm event
will be triggered which a userspace daemon should catch allowing it to
extend the pool device. Only one such event will be sent.
-Resuming a device with a new table itself triggers an event so the
-userspace daemon can use this to detect a situation where a new table
-already exceeds the threshold.
+
+No special event is triggered if a just resumed device's free space is below
+the low water mark. However, resuming a device always triggers an
+event; a userspace daemon should verify that free space exceeds the low
+water mark when handling this event.
A low water mark for the metadata device is maintained in the kernel and
will trigger a dm event if free space on the metadata device drops below