Searched refs:threads (Results 51 – 75 of 205) sorted by relevance
123456789
| /Zephyr-latest/samples/philosophers/ |
| D | README.rst | 12 preemptible and cooperative threads of differing priorities, as well as dynamic mutexes and thread
39 In these cases, the philosopher threads will run with priorities 0 to 5 (preempt-only) and -7 to -2
72 tools like OpenOCD and J-link to inspect thread data using ``info threads``.
91 (gdb) i threads
126 (gdb) i threads
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | queues.rst | 7 threads and ISRs to add and remove data items of any size. The queue is similar
|
| D | message_queues.rst | 7 message queue, allowing threads and ISRs to asynchronously send and receive
39 Any number of sending threads may wait simultaneously when the ring buffer
49 Any number of receiving threads may wait simultaneously when the ring buffer
108 to pass data items from a producing thread to one or more consuming threads.
139 to process data items generated by one or more producing threads. Note that
165 head of the queue that is generated by one or more producing threads.
185 Use a message queue to transfer small data items between threads
|
| D | mailboxes.rst | 8 A mailbox allows threads to send and receive messages of any size
25 * A **receive queue** of threads that are waiting to receive a message.
30 A mailbox allows threads, but not ISRs, to exchange messages.
37 allowing both threads participating in an exchange to know
47 a message exchange between compatible sending and receiving threads.
49 allowing both threads to know what has occurred.
84 and receiving thread are satisfied; such threads are said to be **compatible**.
108 consumed by receiving threads. The asynchronous exchange technique provides an
221 (or set of sending threads) at any point in time.
316 Any number of receiving threads may wait simultaneously on a mailboxes'
[all …]
|
| D | pipes.rst | 46 streaming data between threads.
83 thread to one or more consumer threads. If the pipe's ring buffer fills up,
206 Pipes are useful for sending streams of data between threads. Typical
210 - Streaming logs or packets between threads.
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | system_threads.rst | 13 The kernel spawns the following system threads:
21 threads, the main thread uses the lowest configured cooperative thread
42 Additional system threads may also be spawned, depending on the kernel
|
| /Zephyr-latest/tests/arch/arm/arm_thread_swap/ |
| D | README.txt | 38 - threads in system calls are using the privileged thread stack
40 user threads in PRIV mode and supervisor threads
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | semaphores.rst | 36 Any number of threads may wait on an unavailable semaphore simultaneously.
42 of threads able to execute the critical section at the same time. You may also
123 Use a semaphore to control access to a set of resources by multiple threads.
126 threads or ISRs.
|
| D | mutexes.rst | 7 reentrant mutex. A mutex allows multiple threads to safely share
40 for as short a time as possible to avoid negatively impacting other threads
42 it must **unlock** the mutex to allow other threads to use the resource.
44 Any number of threads may wait on a locked mutex simultaneously.
89 shared between threads of different priorities.
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 13 this feature. If there are two Zephyr application threads runnable on
83 threads. The kernel will ensure that only one thread across all CPUs
101 kernel scheduler to decide on which threads to execute. Zephyr
106 By default, new threads can run on any CPU. Calling
160 two CPUs and two app threads which begin operating simultaneously.
219 will not work to synchronously run new threads. The workaround in
223 involve severe lock contention) for new threads. The expectation is
234 scheduling the highest N priority ready threads to execute. When CPU masking
235 is used, there may be more than one valid set of threads (not to be confused
236 with an optimal set of threads) that can be scheduled on the N CPUs and a
[all …]
|
| /Zephyr-latest/lib/libc/common/ |
| D | Kconfig | 108 bool "C11 <threads.h> API support"
111 # of C11 threads and POSIX API can be abstracted out to a common library.
115 Common implementation of C11 <threads.h> API.
|
| /Zephyr-latest/arch/arc/core/dsp/ |
| D | Kconfig | 26 across context switches to allow multiple threads to perform concurrent
50 across context switches to allow multiple threads to perform concurrent
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.pthread | 10 Select 'y' here to enable POSIX threads, mutexes, condition variables, and thread-specific
19 int "Maximum number of POSIX threads"
22 Maximum simultaneously active threads in a POSIX application.
98 bool "Run POSIX threads with different priorities and schedulers"
101 scheduling algorithms for different threads via functions such as pthread_setschedparam()
|
| /Zephyr-latest/cmake/toolchain/iar/ |
| D | Kconfig.defconfig | 47 # ICCARM does not support <threads.h>
|
| /Zephyr-latest/samples/kernel/condition_variables/condvar/ |
| D | README.rst | 14 become true. Different threads alternate between their entry point
66 Main(): Waited and joined with 3 threads. Final value of count = 145. Done.
|
| /Zephyr-latest/doc/develop/languages/c/ |
| D | common_libc.rst | 32 threads. The size of the internal memory heap is specified by the
46 multiple threads. These functions are implemented in
|
| /Zephyr-latest/samples/subsys/portability/cmsis_rtos_v1/philosophers/ |
| D | README.rst | 12 threads of differing priorities, as well as mutex/semaphore and thread sleeping
55 usage of multiple preemptible threads of differing
|
| /Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/philosophers/ |
| D | README.rst | 12 threads of differing priorities, as well as mutex/semaphore and thread sleeping
55 usage of multiple preemptible threads of differing
|
| /Zephyr-latest/samples/net/sockets/socketpair/ |
| D | README.rst | 5 Implement communication between threads using socket pairs.
37 After the sample starts, several client threads are spawned. Each client
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | virtual_memory.rst | 151 * Stacks for user mode threads are automatically granted read-write access
152 to their corresponding user mode threads during thread creation.
154 * Global variables, by default, are not accessible to user mode threads.
156 use global variables in user mode threads, and on how to share data
157 between user mode threads.
|
| /Zephyr-latest/subsys/rtio/ |
| D | Kconfig.workq | 24 int "Number of threads to use for processing work-items"
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.obj_core | 100 bool "Integrate threads into object core framework"
103 When enabled, this option integrates threads into the object core
138 bool "Object core statistics for threads"
|
| /Zephyr-latest/subsys/tracing/sysview/ |
| D | sysview_config.c | 62 for (thread = _kernel.threads; thread; thread = thread->next_thread) { in send_task_list_cb()
|
| /Zephyr-latest/samples/userspace/shared_mem/ |
| D | README.rst | 4 Use memory partitioning to protect memory between threads.
8 This sample is an example of running multiple threads assigned
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | float.rst | 6 The kernel allows threads to use floating point registers on board
33 This mode is used when the application has no threads that use floating point
51 The behavior is undefined, if two or more threads attempt to use
53 (or prevent) multiple threads from using these registers.
58 This mode is used when the application has two or more threads that use
83 treats *all* threads as FPU users when shared FP registers mode is enabled.
109 context of threads that are not using the FP registers.
125 * Lazy stacking is activated by default on threads that are pretagged with
127 * Lazy stacking is activated dynamically on threads that are not pretagged with
186 context of threads that are not using the FP registers. An extra 16 bytes
[all …]
|
123456789
