diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2017-03-12 11:59:43 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska-skaware@skarnet.org> | 2017-03-12 11:59:43 +0000 |
| commit | c60ebd422171808ad58b936914055397bb205bef (patch) | |
| tree | 7db3e5728d72ad209f8e22b9eb9f337e0b0c3e58 /doc/libs6/s6lockd-helper.html | |
| parent | e28fe5908a91d8795ca9923d64eeed7d3e898434 (diff) | |
| download | s6-c60ebd422171808ad58b936914055397bb205bef.tar.xz | |
Adapt to skalibs-2.5.0.0
Diffstat (limited to 'doc/libs6/s6lockd-helper.html')
| -rw-r--r-- | doc/libs6/s6lockd-helper.html | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/libs6/s6lockd-helper.html b/doc/libs6/s6lockd-helper.html index 281c7e8..7a7d80a 100644 --- a/doc/libs6/s6lockd-helper.html +++ b/doc/libs6/s6lockd-helper.html @@ -43,7 +43,8 @@ threads) to implement timed lock acquisition. This can lead to a lot of s6lockd-helper processes, but this is not a problem: <ul> <li> Processes are not a scarce resource. Today's schedulers work in O(1), -i.e. a sleeping process takes no scheduling time at all. </li> +or in O(a function of the number of runnable processes), which means that a +sleeping process takes no scheduling time at all </li> <li> s6lockd-helper is extremely tiny. Every instance should use up at most one or two pages of non-sharable memory. </li> </ul> </li> |