summaryrefslogtreecommitdiff
path: root/Documentation/admin-guide/device-mapper/dm-crypt.rst
diff options
context:
space:
mode:
authorJani Nikula <jani.nikula@intel.com>2024-09-30 11:49:10 +0300
committerJani Nikula <jani.nikula@intel.com>2024-09-30 11:49:10 +0300
commite0568571258d096f0277c74185bcbfc9cf21bccb (patch)
treea380953643dbb86bffaa862d11e58eba22697988 /Documentation/admin-guide/device-mapper/dm-crypt.rst
parent9d5a05f86d2f4f81abcac6abc856c0d511a8607b (diff)
parent9852d85ec9d492ebef56dc5f229416c925758edc (diff)
Merge drm/drm-next into drm-intel-next
Sync to v6.12-rc1. Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'Documentation/admin-guide/device-mapper/dm-crypt.rst')
-rw-r--r--Documentation/admin-guide/device-mapper/dm-crypt.rst15
1 files changed, 12 insertions, 3 deletions
diff --git a/Documentation/admin-guide/device-mapper/dm-crypt.rst b/Documentation/admin-guide/device-mapper/dm-crypt.rst
index 552c9155165d..9f8139ff97d6 100644
--- a/Documentation/admin-guide/device-mapper/dm-crypt.rst
+++ b/Documentation/admin-guide/device-mapper/dm-crypt.rst
@@ -160,15 +160,24 @@ iv_large_sectors
The <iv_offset> must be multiple of <sector_size> (in 512 bytes units)
if this flag is specified.
+integrity_key_size:<bytes>
+ Use an integrity key of <bytes> size instead of using an integrity key size
+ of the digest size of the used HMAC algorithm.
-Module parameters::
+Module parameters::
max_read_size
+ Maximum size of read requests. When a request larger than this size
+ is received, dm-crypt will split the request. The splitting improves
+ concurrency (the split requests could be encrypted in parallel by multiple
+ cores), but it also causes overhead. The user should tune this parameters to
+ fit the actual workload.
+
max_write_size
- Maximum size of read or write requests. When a request larger than this size
+ Maximum size of write requests. When a request larger than this size
is received, dm-crypt will split the request. The splitting improves
concurrency (the split requests could be encrypted in parallel by multiple
- cores), but it also causes overhead. The user should tune these parameters to
+ cores), but it also causes overhead. The user should tune this parameters to
fit the actual workload.