| /Zephyr-Core-3.4.0/samples/kernel/metairq_dispatch/src/ |
| D | main.c | 22 } threads[NUM_THREADS]; variable
40 } threads[NUM_THREADS]; member
64 int ret = k_msgq_put(&threads[m.target].msgq, &m, K_NO_WAIT); in metairq_fn()
130 int lidx = stats.threads[t].nevt++; in record_latencies()
132 if (lidx < ARRAY_SIZE(stats.threads[t].latencies)) { in record_latencies()
133 stats.threads[t].latencies[lidx] = latency; in record_latencies()
160 if (stats.threads[i].nevt == 0) { in record_latencies()
165 calc_stats(stats.threads[i].latencies, in record_latencies()
166 stats.threads[i].nevt, in record_latencies()
188 int ret = k_msgq_get(&threads[id].msgq, &m, K_FOREVER); in thread_fn()
[all …]
|
| /Zephyr-Core-3.4.0/subsys/portability/cmsis_rtos_v2/ |
| D | Kconfig | 23 Mention max number of threads in CMSIS RTOS V2 compliant application.
24 There's a limitation on the number of threads due to memory
32 Mention max number of dynamic threads in CMSIS RTOS V2 compliant
33 application. There's a limitation on the number of threads due to memory
34 related constraints. Dynamic threads are a subset of all other CMSIS
35 threads i.e. they also count towards that maximum too.
38 int "Max stack size threads can be allocated in CMSIS RTOS V2 application"
42 Mention max stack size threads can be allocated in CMSIS RTOS V2 application.
45 int "Dynamic stack size threads are allocated in CMSIS RTOS V2 application"
49 Mention dynamic stack size threads are allocated in CMSIS RTOS V2 application.
|
| /Zephyr-Core-3.4.0/tests/arch/common/timing/src/ |
| D | main.c | 19 static struct k_thread threads[MAX_NUM_THREADS]; variable
108 k_thread_create(&threads[i], tstack[i], STACK_SIZE, in ZTEST()
111 k_thread_cpu_mask_enable(&threads[i], i); in ZTEST()
112 k_thread_start(&threads[i]); in ZTEST()
116 k_thread_join(&threads[i], K_FOREVER); in ZTEST()
|
| /Zephyr-Core-3.4.0/doc/kernel/services/scheduling/ |
| D | index.rst | 6 The kernel's priority-based scheduler allows an application's threads
39 to be the current thread. When multiple ready threads of the same priority
44 (:kconfig:option:`CONFIG_SCHED_DEADLINE`) and a choice of threads have equal
47 enabled, two threads are only considered to have the same priority when both
55 cooperative threads and preemptive threads.
60 runtime overhead and performance scaling when many threads are added.
65 very fast constant time performance for single threads and very low code size.
67 that will never see more than a small number (3, maybe) of runnable threads in
77 quickly into the many thousands of threads.
79 Use this for applications needing many concurrent runnable threads (> 20 or
[all …]
|
| /Zephyr-Core-3.4.0/doc/kernel/usermode/ |
| D | overview.rst | 9 User mode threads are considered to be untrusted by Zephyr and are therefore
10 isolated from other user mode threads and from the kernel. A flawed or
22 cannot compromise the kernel or other threads.
25 with their own group of threads and private data structures, which are
31 For threads running in a non-privileged CPU state (hereafter referred to as
52 threads in the same memory domain, depending on hardware.
54 - On MPU systems, threads may only access their own stack buffer.
56 - On MMU systems, threads may access any user thread stack in the same
59 - By default, program text and read-only data are accessible to all threads
62 - User threads by default are not granted default access to any memory
[all …]
|
| D | index.rst | 6 Zephyr offers the capability to run threads at a reduced privilege level
10 For details on creating threads that run in user mode, please see
|
| 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-Core-3.4.0/lib/posix/getopt/ |
| D | Kconfig | 12 All not shell threads share one global instance of getopt state, hence
14 for other threads by extending function getopt_state_get in
25 All not shell threads share one global instance of getopt state, hence
27 for other threads by extending function getopt_state_get in
|
| /Zephyr-Core-3.4.0/tests/benchmarks/sched_userspace/src/ |
| D | main.c | 68 static k_tid_t threads[MAX_NB_THREADS]; variable
85 threads[tid] = k_thread_create(&app_threads[tid].thread, in exec_test()
100 k_thread_start(threads[tid]); in exec_test()
103 k_thread_join(threads[tid], K_FOREVER); in exec_test()
|
| /Zephyr-Core-3.4.0/samples/philosophers/src/ |
| D | main.c | 219 k_thread_create(&threads[i], &stacks[i][0], STACK_SIZE, in start_threads()
226 k_thread_name_set(&threads[i], tname); in start_threads()
228 k_object_access_grant(fork(i), &threads[i]); in start_threads()
229 k_object_access_grant(fork((i + 1) % NUM_PHIL), &threads[i]); in start_threads()
231 k_thread_start(&threads[i]); in start_threads()
|
| /Zephyr-Core-3.4.0/tests/kernel/common/src/ |
| D | timeout_order.c | 36 static struct k_thread threads[NUM_TIMEOUTS]; variable
56 (void)k_thread_create(&threads[ii], stacks[ii], STACKSIZE, in ZTEST()
87 k_thread_join(&threads[ii], K_FOREVER); in ZTEST()
|
| 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-Core-3.4.0/samples/arch/smp/pi/ |
| D | README.rst | 8 This sample application calculates Pi independently in many threads, and
19 number of threads to use (``THREADS_NUM``).
40 Calculate first 240 digits of Pi independently by 16 threads.
46 All 16 threads executed by 4 cores in 28 msec
|
| /Zephyr-Core-3.4.0/doc/kernel/services/synchronization/ |
| D | events.rst | 16 event object is referenced by its memory address. One or more threads may wait
18 event object. When new events are delivered to the event object, all threads
32 conditions of multiple threads waiting on the event object. All threads whose
36 the requested events, or for any of them. Furthermore, threads making a wait
39 multiple threads wait on the same event object.
83 /* notify threads that data is available */
104 /* notify threads that more data is available */
160 Use events to pass small amounts of data to multiple threads at once.
|
| 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-Core-3.4.0/samples/basic/threads/ |
| D | README.rst | 9 This example demonstrates spawning multiple threads using
10 :c:func:`K_THREAD_DEFINE`. It spawns three threads. Each thread is then defined
19 When either of these threads toggles its LED, it also pushes information into a
48 :zephyr-app: samples/basic/threads
|
| /Zephyr-Core-3.4.0/tests/kernel/pending/ |
| D | README.txt | 5 This test verifies that preemptible threads can pend on the following
36 Testing preemptible threads block on fifos ...
39 Testing preemptible threads block on lifos ...
|
| /Zephyr-Core-3.4.0/include/zephyr/sys/ |
| D | p4wq.h | 83 struct k_thread *threads; member
108 .threads = _p4threads_##name, \
135 .threads = _p4threads_##name, \
|
| /Zephyr-Core-3.4.0/tests/subsys/logging/log_immediate/src/ |
| D | log_immediate_test.c | 30 static struct k_thread threads[NUM_THREADS]; variable
64 tids[i] = k_thread_create(&threads[i], stacks[i], STACK_SIZE, in ZTEST()
|
| /Zephyr-Core-3.4.0/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_posix platforms. In that emulation environment, threads will
88 (intended) for non-cooperative threads like T2 and T3 which is attributed to delays
|
| /Zephyr-Core-3.4.0/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-Core-3.4.0/drivers/wifi/eswifi/ |
| D | Kconfig.eswifi | 34 int "esWiFi threads priority"
37 This option sets the priority of the esWiFi threads.
|
| /Zephyr-Core-3.4.0/samples/userspace/syscall_perf/ |
| D | README.rst | 15 Then both threads call k_current_get() which returns a reference to the
18 Both threads are showing the number of core clock cycles and the number of
|
| /Zephyr-Core-3.4.0/include/zephyr/debug/ |
| D | object_tracing.h | 19 #define SYS_THREAD_MONITOR_HEAD ((struct k_thread *)(_kernel.threads))
|
| /Zephyr-Core-3.4.0/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.
|
