Searched refs:threads (Results 1 – 24 of 24) sorted by relevance

/manual/
A D	threads.texi	5 @cindex threads 9 POSIX threads. 19 @cindex ISO C threads 20 @cindex C threads 21 @pindex threads.h 48 @standards{C11, threads.h} 53 @standards{C11, threads.h} 57 @standards{C11, threads.h} 62 @standards{C11, threads.h} 66 @standards{C11, threads.h} [all …]
A D	process.texi	191 On Linux, threads created by @code{pthread_create} also receive a 194 subsequently created threads are distinct. They are allocated from 197 contrast to processes, threads are never waited for explicitly, so a 199 canceled. This is true even for joinable threads, not just detached 200 threads. Threads are assigned to a @dfn{thread group}. In 202 thread group ID of all threads in the process. 237 especially regarding reuse of the IDs of threads which have exited.
A D	intro.texi	203 of other threads. MT, in MT-Safe, stands for Multi Thread. 211 concurrent calls in other threads may interfere in a destructive way. 479 after other threads are started. 662 in which changes made by other threads are lost. Thus, functions marked 716 are not to be called when multiple threads are running or asynchronous 744 not to be called when multiple threads are running or asynchronous 773 are not to be called when multiple threads are running or asynchronous 837 threads or within asynchronous signal or cancellation handlers.
A D	resource.texi	694 thread IDs, and control how specific threads are scheduled with 1196 and threads run can be to some extend be control with the scheduling 1207 making progress by other processes or threads using CPU resources. In 1347 retrieve the information for different POSIX threads. A separate 1565 The use of threads or processes with shared memory allows an application 1618 Before starting more threads it should be checked whether the processors
A D	crypt.texi	147 threads simultaneously, and the string it returns will be overwritten 168 It can safely be used from multiple threads, as long as different
A D	math.texi	1539 @c is internally protected by a lock, although other threads may modify 1579 which is shared by all threads. The state is not directly accessible to 1645 by all threads of the process. The second requires the user to handle 1815 threads. For this reason all the above functions have a counterpart 1819 Please note that it is no problem if several threads use the global 1820 state if all threads use the functions which take a pointer to an array 1822 same loop but if the state in the array is different all threads will
A D	sysinfo.texi	525 fstab}. This variable is shared by all threads and therefore this 547 fstab}. This variable is shared by all threads and therefore this 569 fstab}. This variable is shared by all threads and therefore this 733 used in situations where multiple threads access the file.
A D	Makefile	41 nss users sysinfo conf crypt debug threads \
A D	errno.texi	1172 all threads in the process, it returns a private copy for the 1417 The variable is global and shared by all threads. 1424 variable is global and shared by all threads. 1435 is global and shared by all threads.
A D	memory.texi	285 The presence of multiple arenas allows multiple threads to allocate 352 @c threads are active that is regarded as unsafe. An arena's next field 710 @c threads are running malloc and have their own arenas locked when 1319 @c threads, and it may find a partial update if called from a signal 1564 @c regard to other threads, signals or cancellation. 3099 New threads and subprocesses inherit the access rights of the current 3100 thread. If a protection key is allocated subsequently, existing threads 3165 below). Access rights of other threads are not changed. 3201 protection key. The calling thread and other threads may retain access
A D	llio.texi	523 @c therefore multiple threads / kernel tasks may race and get the same offset 534 @c happen if two threads start the write at the same time. Only writes that 539 @c "2.9.7 Thread Interactions with Regular File Operations" that threads 2319 kernel (if available) or using an implementation based on threads at 3219 implementation which uses threads for handling the enqueued requests. 3234 This member specifies the maximal number of threads which may be used 4450 access between threads within the same process by having each thread perform 4467 by the threads inside a process, and thus cannot be used by one thread 4477 This example creates three threads each of which loops five times, 4486 (typically manifested as missing lines) as some threads race in and
A D	platform.texi	133 all threads in the current process. Setting the
A D	stdio.texi	317 threads race to allocate the same file descriptor number. To avoid the 482 @cindex threads 487 these also if the program one writes never use threads since the design 493 threads at the same time will cause the operations to be executed as if 570 calls by the same threads is necessary to unlock the stream completely. 612 used in a context where two or more threads may use a stream at a time. 626 introduction of threads) were implemented as macros which are very fast 3002 @c so we're ruling out the use of this extension with threads. Calling 3255 @c threads may be changing it and the possbility of leaving the stream
A D	contrib.texi	500 Adhemerval Zanella for optimized functions on PowerPC, ISO C threads support
A D	filesys.texi	509 multiple threads, unless you use your own locking to ensure that 512 @code{readdir} from multiple threads as long as each thread uses 529 threads the result is stored inside the @var{entry} object. 555 the rare case that multiple threads need to read from the same 621 @c other threads could still be using the dir stream while it's closed. 1050 all the threads as a group, and therefore it is a good idea to supply a
A D	setjmp.texi	397 Since the context contains information about the stack no two threads
A D	charset.texi	810 @c concurrently in other threads, this function behaves safely as long 1302 multiple conversions at the same time (not only when using threads) 1606 threads. 1704 It is not possible to use the same descriptor in different threads to
A D	tunables.texi	417 The behavior of POSIX threads can be tuned to gain performance improvements
A D	users.texi	298 @c implement threads. 301 @c threads that are not exiting, signal them until no thread remains 1108 @c They're both modified while holding a lock, but other threads may
A D	startup.texi	14 independently of the other copies. Though it may have multiple threads
A D	locale.texi	228 @c once threads are started. It takes a write lock itself, but it may
A D	time.texi	1060 all threads. POSIX.1c introduced a variant of this function. 2850 @c is shared by all threads of a process, so calling it in one thread
A D	terminal.texi	1687 @c implementation may leave the break enabled if cancelled, and threads
/manual/examples/
A D	ofdlocks.c	68 pthread_t threads[NUM_THREADS]; in main() local 73 pthread_create (&threads[i], NULL, thread_start, (void *) i); in main()

Completed in 617 milliseconds

Last Index update Sun Aug 20 00:31:31 CST 2023