Lines Matching refs:to

8 poor way to do multithreaded programming. It is much better to formulate
13 -  Matching parallelism to available resources
37 threads to keep the physical threads working. *Oversubscription* occurs
39 Oversubscription usually leads to *time sliced* execution of logical
41 Time Slicing*. The scheduler tries to avoid oversubscription, by having
42 one logical thread per physical thread, and mapping tasks to logical
62 to undertake without understanding the higher-level organization of a
69 The scheduler does *load balancing*. In addition to using the right
70 number of threads, it is important to distribute work evenly across
72 tasks, the scheduler usually does a good job of assigning tasks to
73 threads to balance load. With thread-based programming, you are often
74 stuck dealing with load-balancing yourself, which can be tricky to get
79    Design your programs to try to create many more tasks than there are
80    threads, and let the task scheduler choose the mapping from tasks to
86 programming, you are forced to think at the low level of physical
87 threads to get good efficiency, because you have one logical thread per
88 physical thread to avoid undersubscription or oversubscription. You also
89 have to deal with the relatively coarse grain of threads. With tasks,
91 the efficient scheduling to the scheduler.