diff options
| author |   Daniel Yang <danielyangkang@gmail.com> | 2024-08-07 02:01:21 -0700 |
|---|---|---|
| committer |   Mikulas Patocka <mpatocka@redhat.com> | 2024-08-13 16:36:39 +0200 |
| commit | 86cfa9a85fb04fa61e7c6b5a8ecf812437cdad78 (patch) | |
| tree | cb5cc3ca261aaef1f02fde7cb037f434c31b4bb8 | |
| parent | dm resume: don't return EINVAL when signalled (diff) | |
| download | wireguard-linux-86cfa9a85fb04fa61e7c6b5a8ecf812437cdad78.tar.xz wireguard-linux-86cfa9a85fb04fa61e7c6b5a8ecf812437cdad78.zip | |
Documentation: dm-crypt.rst warning + error fix
While building kernel documention using make htmldocs command, I was
getting unexpected indentation error. Single description was given for
two module parameters with wrong indentation. So, I corrected the
indentation of both parameters and the description.
Signed-off-by: Shibu kumar <shibukumar.bit@gmail.com>
Signed-off-by: Daniel Yang <danielyangkang@gmail.com>
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Fixes: 0d815e3400e6 ("dm-crypt: limit the size of encryption requests")
| -rw-r--r-- | Documentation/admin-guide/device-mapper/dm-crypt.rst | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/Documentation/admin-guide/device-mapper/dm-crypt.rst b/Documentation/admin-guide/device-mapper/dm-crypt.rst index e625830d335e..552c9155165d 100644 --- a/Documentation/admin-guide/device-mapper/dm-crypt.rst +++ b/Documentation/admin-guide/device-mapper/dm-crypt.rst @@ -162,13 +162,14 @@ iv_large_sectors Module parameters:: -max_read_size -max_write_size - Maximum size of read or 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 - fit the actual workload. + + max_read_size + max_write_size + Maximum size of read or 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 + fit the actual workload. Example scripts |