dm-verity: update the documention about try_verify_in_tasklet

Commit Message

LongPing Wei March 28, 2025, 12:42 a.m. UTC

Tasklets aren't actually used anymore.

Signed-off-by: LongPing Wei <[e-mail]>
---
 Documentation/admin-guide/device-mapper/verity.rst | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

Patch

diff --git a/Documentation/admin-guide/device-mapper/verity.rst b/Documentation/admin-guide/device-mapper/verity.rst
index cda958a517c6..9382343c99d2 100644
--- a/Documentation/admin-guide/device-mapper/verity.rst
+++ b/Documentation/admin-guide/device-mapper/verity.rst
@@ -151,10 +151,11 @@  root_hash_sig_key_desc <key_description>
     already in the secondary trusted keyring.
 
 try_verify_in_tasklet
-    If verity hashes are in cache, verify data blocks in kernel tasklet instead
-    of workqueue. This option can reduce IO latency. The size limits could be
-    configured via /sys/module/dm_verity/parameters/use_bh_bytes. The four
-    parameters correspond to limits for IOPRIO_CLASS_NONE,IOPRIO_CLASS_RT,
+    If verity hashes are in cache and the IO size does not exceed the limit,
+    verify data blocks in bottom half instead of workqueue. This option can
+    reduce IO latency. The size limits can be configured via
+    /sys/module/dm_verity/parameters/use_bh_bytes. The four parameters
+    correspond to limits for IOPRIO_CLASS_NONE,IOPRIO_CLASS_RT,
     IOPRIO_CLASS_BE and IOPRIO_CLASS_IDLE in turn.
     For example:
     <none>,<rt>,<be>,<idle>