From 865c6ca2278d1f3d9d64f6ca787fe8b64e319c4d Mon Sep 17 00:00:00 2001 From: Vesa Karvonen Date: Mon, 21 Oct 2024 21:06:47 +0300 Subject: [PATCH] Wordsmithing --- lib/picos_std.awaitable/picos_std_awaitable.mli | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/lib/picos_std.awaitable/picos_std_awaitable.mli b/lib/picos_std.awaitable/picos_std_awaitable.mli index a1ca009a..3f692c38 100644 --- a/lib/picos_std.awaitable/picos_std_awaitable.mli +++ b/lib/picos_std.awaitable/picos_std_awaitable.mli @@ -145,10 +145,11 @@ end ]} The above mutex outperforms most other mutexes under both no/low and high - contention scenarios. In no/low contention scenarios the use - [fetch_and_add] provides low overhead. In high contention scenarios the - above mutex allows unfairness, which avoids - {{:https://en.wikipedia.org/wiki/Lock_convoy} lock convoy}. + contention scenarios. In no/low contention scenarios the use of + {{!Awaitable.fetch_and_add} [fetch_and_add]} provides low overhead. In high + contention scenarios the above mutex allows unfairness, which avoids + performance degradation due to the + {{:https://en.wikipedia.org/wiki/Lock_convoy} lock convoy} phenomena. {2 [Condition]}