blob: 39203333569fbbd69ac9994738c58d1d18f0410b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
[[!tag open_issue_hurd]]
Hurd servers / VFS libraries are multithreaded, roughly using one thread per
incoming request. This is not the best approach: it doesn't really make sense
to scale the number of worker threads with the number of incoming requests, but
instead they should be scaled according to the backends' characteristics.
The [[hurd/Critique]] should have some more on this.
Alternative approaches:
* Continuation-passing style
* [[microkernel/Mach]] internally [[uses
continuations|microkernel/mach/continuation]], too.
* [[Erlang-style_parallelism]]
* [libtcr - Threaded Coroutine Library](http://oss.linbit.com/libtcr/)
* <http://monkey.org/~provos/libevent/>
---
See also: [[multiprocessing]].
|
