Documentation: dm-crypt.rst warning + error fix
Subsystems (2)
PATCH 1/1 Documentation: dm-crypt.rst warning + error fix
Signed-off-by Daniel Yang <[email protected]>
--- .../admin-guide/device-mapper/dm-crypt.rst | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-)
Documentation/admin-guide/device-mapper/dm-crypt.rst +8 -7
@@ -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
Signature · 1 line
2.39.2
Jonathan Corbet
maintainerQuoted 18 lines · Daniel Yang
Signed-off-by Daniel Yang <[email protected]>--- .../admin-guide/device-mapper/dm-crypt.rst | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-)Documentation/admin-guide/device-mapper/dm-crypt.rst +0
-5@@ -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
Documentation/admin-guide/device-mapper/dm-crypt.rst iv_large_sectors · line 172
Quoted 10 lines
Documentation/admin-guide/device-mapper/dm-crypt.rst +8
-2- 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.
Thanks for the patch. It would have been better to include a proper changelog, even for a simple change like this. Unfortunately, I got another fix for this error a few days ago, and have applied that.
jon