| /Zephyr-latest/tests/kernel/common/src/ |
| D | errno.c | 26 static struct k_thread threads[N_THREADS]; variable
86 k_thread_create(&threads[ii], stacks[ii], STACK_SIZE, in ZTEST()
108 k_thread_join(&threads[ii], K_FOREVER); in ZTEST()
|
| /Zephyr-latest/samples/kernel/metairq_dispatch/ |
| D | README.rst | 13 to asynchronous queues feeding several worker threads, each running at
20 running threads and delay scheduling of lower priority threads.
35 * On average, higher priority (lower numbered) threads have better
38 * Cooperatively scheduled threads have significantly better processing
42 * Because of queueing and the bursty load, all worker threads of any
49 other threads, including cooperative ones that cannot normally be
56 preemption of running threads by interrupts, a working timer driver,
63 native_sim platforms. In that emulation environment, threads will
88 (intended) for non-cooperative threads like T2 and T3 which is attributed to delays
|
| /Zephyr-latest/include/zephyr/sys/ |
| D | p4wq.h | 95 struct k_thread *threads; member
122 .threads = _p4threads_##name, \
161 .threads = _p4threads_##name, \
|
| /Zephyr-latest/tests/benchmarks/sched_userspace/ |
| D | README.rst | 7 abstractions. Contrary to the non-userspace version, it runs threads
11 threads at a higher priority, from this initial state:
|
| /Zephyr-latest/samples/posix/philosophers/src/ |
| D | main.c | 36 static pthread_t threads[NUM_PHIL]; variable
220 ret = pthread_create(&threads[i], NULL, philosopher, INT_TO_POINTER(i)); in start_threads()
229 ret = pthread_setschedparam(threads[i], policy, ¶m); in start_threads()
240 pthread_setname_np(threads[i], tname); in start_threads()
|
| /Zephyr-latest/subsys/portability/cmsis_rtos_v2/ |
| D | Kconfig | 23 Max number of threads in CMSIS RTOS V2 application that can be created with
31 Max number of threads in CMSIS RTOS V2 application that can be created with
35 int "Max stack size threads can be allocated in CMSIS RTOS V2 application"
39 Mention max stack size threads can be allocated in CMSIS RTOS V2 application.
42 int "Dynamic stack size threads are allocated in CMSIS RTOS V2 application"
46 Mention dynamic stack size threads are allocated in CMSIS RTOS V2 application.
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 17 Kernel objects are completely opaque to user threads. User threads work
21 user threads.
23 Since user threads may not directly manipulate kernel objects, all use of
44 Kernel objects that are only used by supervisor threads have no restrictions
46 to prevent accidental or intentional corruption by user threads, they must
47 not be located in any memory that user threads have direct access to.
83 * Supervisor threads may call :c:func:`k_object_free` to force a dynamic
86 * If an object's references drop to zero (which happens when no threads have
87 permissions on it) the object will be automatically freed. User threads
90 cleared when a thread terminates. Supervisor threads may additionally
[all …]
|
| /Zephyr-latest/tests/benchmarks/sched_queues/ |
| D | README.rst | 7 number of ready threads increases. This benchmark can be used to help
12 * Time to add a threads of increasing priority to the ready queue.
13 * Time to add threads of decreasing priority to the ready queue.
|
| /Zephyr-latest/include/zephyr/debug/ |
| D | object_tracing.h | 19 #define SYS_THREAD_MONITOR_HEAD ((struct k_thread *)(_kernel.threads))
|
| /Zephyr-latest/samples/basic/threads/ |
| D | CMakeLists.txt | 5 project(threads) project
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | condvar.rst | 7 that enables threads to wait until a particular condition occurs.
22 A condition variable is basically a queue of threads that threads can put
31 of those waiting threads and thus allow them to continue by signaling on
97 one thread or by calling :c:func:`k_condvar_broadcast` for multiple threads.
|
| /Zephyr-latest/doc/kernel/services/ |
| D | index.rst | 33 threads/index.rst
35 threads/system_threads.rst
36 threads/workqueue.rst
37 threads/nothread.rst
52 threads and ISRs.
|
| /Zephyr-latest/samples/modules/tflite-micro/tflm_ethosu/src/ |
| D | main.cpp | 218 } threads[NUM_JOB_TASKS + NUM_INFERENCE_TASKS]; in main() local
236 auto &thread = threads[nthreads]; in main()
259 auto &thread = threads[nthreads]; in main()
277 k_thread_start(threads[n].id); in main()
|
| /Zephyr-latest/drivers/wifi/eswifi/ |
| D | Kconfig.eswifi | 43 int "esWiFi threads priority"
46 This option sets the priority of the esWiFi threads.
|
| /Zephyr-latest/samples/userspace/syscall_perf/ |
| D | README.rst | 18 Then both threads call :c:func:`k_current_get()` which returns a reference to the
21 Both threads are showing the number of core clock cycles and the number of
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.c_lib_ext | 24 All not shell threads share one global instance of getopt state, hence
26 for other threads by extending function getopt_state_get in
|
| D | Kconfig.xsi_threads_ext | 6 bool "X/Open threads extensions"
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | index.rst | 14 independently executable threads of instructions.
19 Any number of threads can be defined by an application (limited only by
47 By default, threads run in supervisor mode and allow access to
49 peripherals. User mode threads have a reduced set of privileges.
167 schedule state that only applies to **Ready** threads.
205 management data structures which only pertain to user mode threads.
216 If it is known that a stack will need to host user threads, or if this
219 user threads.
236 The scheduler distinguishes between two classes of threads,
254 The scheduler does not make heuristic decisions to re-prioritize threads.
[all …]
|
| /Zephyr-latest/subsys/portability/cmsis_rtos_v1/ |
| D | Kconfig | 18 int "Max stack size threads can be allocated in CMSIS RTOS application"
22 Mention max stack size threads can be allocated in CMSIS RTOS application.
|
| /Zephyr-latest/samples/arch/smp/pktqueue/ |
| D | README.rst | 42 Then in each queue-related thread several(defined in THREADS_NUM) threads are created. Each
48 "receiver" queue the execution of threads(related to pair) are terminated.
56 the number of threads per pair of queues(``THREADS_NUM``),
79 Each of 2 parallel queues is processed by 3 threads on 2 cores and contain 5000 packet headers.
|
| /Zephyr-latest/samples/subsys/zbus/hello_world/ |
| D | README.rst | 5 Make three threads talk to each other using zbus.
9 This sample implements a simple hello world application using zbus to make the threads talk to each…
|
| /Zephyr-latest/tests/benchmarks/wait_queues/ |
| D | README.rst | 11 * Time to add threads of increasing priority to a wait queue
12 * Time to add threads of decreasing priority to a wait queue
|
| /Zephyr-latest/tests/bluetooth/tester/ |
| D | Kconfig | 13 int "BTP CMD threads stack size."
|
| /Zephyr-latest/subsys/llext/ |
| D | CMakeLists.txt | 22 message(WARNING "Running LLEXT extensions from user-space threads on RISC-V is not supported!")
|
| /Zephyr-latest/kernel/ |
| D | Kconfig | 43 threads always preempt preemptible threads.
93 int "Number of very-high priority 'preemptor' threads"
98 threads at these priorities will always be scheduled before
99 threads at lower priorities, EVEN IF those threads are
110 for cooperative threads, this tool probably shouldn't be used
117 mode where threads can set "deadline" deltas measured in
128 SMP mode, allowing applications to pin threads to specific CPUs or
129 disallow threads from running on given CPUs. Note that as currently
131 idle-but-runnable threads, and thus works only with the simple
146 threads have a single "assigned" CPU and they will never be
[all …]
|
