forked from massivethreads/massivethreads
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
80 lines (46 loc) · 3.56 KB
/
README
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
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
MassiveThreads - a Lightweight Thread Library for High Productivity Languages
Sorry, this document probably lacks fundamental information. If you have any question, please ask an e-mail address on the last of this text.
[0] System Requirements
Massivethreads is mainly developed and tested on the following environment:
CPU : x86_64
Operating system : Linux (>=2.6)
C compiler : GCC (>=4.4.1)
It can also work on x86, SPARC64IXfx, and XeonPhi, but not tested well.
[1] How to compile
MassiveThreads can be compiled and installed like many other UNIX programs using the following 3-steps:
$ export PREFIX=[directory to install]
$ ./configure --prefix=$PREFIX
$ make
$ make install
More details about system requirements and installation can be found at docs/install.txt .
[3] How to use
MassiveThreads provides 3 APIs to use, native intefrace, pthread-compatible interface, and TBB-like interface.
(1) Native interface
Native interface provide full access to MassiveThreads functionalities.
To use native interface, please include myth.h and specify include path, library path, and shared library like this:
$ gcc -o foo foo.c -I${PREFIX}/include -L${PREFIX}/lib -lmyth (or -lmyth-native)
libmyth.so provides both native and pthread-compatible interface. so If you want to use OS-level pthreads together with MassiveThreads, please use libmyth-native.so, that does not export pthread-compatible functions.
When using libmyth.so, initialization and termination by myth_init() and myth_fini() are not required, because it is automatically done for pthread-compatibility.
In using libmyth-native.so, they are required. You can control the number of worker threads and default stack size from application using myth_init_withparam() instead of myth_init().
(2) Pthread-compatible interface
Pthread-compatible interface provide the same API with pthreads at binary level.
To use this interface, please write your program as using pthreads, and compile with libmyth-compat.so or libmyth.so(if you want to use native interface at the same time).
Using environmental variables such as LD_PRELOAD, existing binaries using pthreads can be executed on MassiveThreads like this:
$ LD_PRELOAD=${PREFIX}/lib/libmyth.so ./a.out
Caution: Executing programs that depend on unsupported pthreads feature (preemption, signal, thread-local storage[__thread], etc...) is not guaranteed. Calling unimplemented functions may also lead to unexpected behavior. To confirm implemented functions, see myth_if_pthread.c .
(3) TBB-like interface
TBB-like interface provides an API compatible with task_group of Intel Threading Building Block.
For more information, please see docs/mtbb_api.txt .
[4] Runtime configuration
(1) Setting the number of worker threads
MassiveThreads creates worker thraeds based on the process affinity. Thus you can control the number of worker threads and CPU cores used by 'taskset' command.
Environmental variable MYTH_WORKER_NUM can also be used to change the number of worker threads (= # of CPU cores used).
By default, MassiveThreads uses all the CPU cores in the machine.
(2) Setting the default stack size
Setting environmental variable MYTH_DEF_STKSIZE (in bytes), you can change the default stack size. By default, MassiveThreads uses 16KB as a default stack size.
[5] Contact
If you have any question, please ask the following address.
Jun Nakashima : nakashima@eidos.ic.i.u-tokyo.ac.jp
[6] License
MassiveThreads is distributed under 2-clause BSD license. See COPYRIGHT for details.
# "myth" is the initial codename of MassiveThreads and no more special meaning than it.