Documentation/core-api: fix spelling mistake in workqueue
Subsystems (2)
PATCH 1/1 Documentation/core-api: fix spelling mistake in workqueue
Correct to "following" from "followings" in the sentence "The followings are the read bandwidths and CPU utilizations depending on different affinity scope settings on ``kcryptd`` measured over five runs."
Signed-off-by Attreyee Mukherjee <[email protected]>
--- Documentation/core-api/workqueue.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/core-api/workqueue.rst +1 -1
@@ -446,7 +446,7 @@ The command used: :: There are 24 issuers, each issuing 64 IOs concurrently. ``--verify=sha512`` makes ``fio`` generate and read back the content each time which makes -execution locality matter between the issuer and ``kcryptd``. The followings +execution locality matter between the issuer and ``kcryptd``. The following are the read bandwidths and CPU utilizations depending on different affinity scope settings on ``kcryptd`` measured over five runs. Bandwidths are in MiBps, and CPU util in percents.
Signature · 1 line
2.34.1
Quoted 14 lines · attreyee-muk
Correct to "following" from "followings" in the sentence "The followings are the read bandwidths and CPU utilizations depending on different affinity scope settings on ``kcryptd`` measured over five runs."
Signed-off-by Attreyee Mukherjee <[email protected]>--- Documentation/core-api/workqueue.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Documentation/core-api/workqueue.rst +0
-0
Documentation/core-api/workqueue.rst The command used: :: · line 451
Quoted 7 lines
Documentation/core-api/workqueue.rst +1
-1@@ -446,7 +446,7 @@ The command used: :: There are 24 issuers, each issuing 64 IOs concurrently. ``--verify=sha512`` makes ``fio`` generate and read back the content each time which makes -execution locality matter between the issuer and ``kcryptd``. The followings +execution locality matter between the issuer and ``kcryptd``. The following are the read bandwidths and CPU utilizations depending on different affinity scope settings on ``kcryptd`` measured over five runs. Bandwidths are in
Applied, thanks.
jon