Searched full:amounts (Results 1 – 21 of 21) sorted by relevance
36 each thread in the tests. This generates large amounts of output. To
32 lower the amounts of input events. Set to 0 for no filtering
20 # This test consumes large amounts of stack when loading the LLEXT.
30 * of time. Since different devices take different amounts of time to perform
15 - Store and access large amounts of date from your system board
45 Zephyr streams non-trivial amounts of data, while still taking a51 Thus the application can be used to test transfers of much larger amounts
22 Builtin command processors rarely add large amounts of
160 Use events to pass small amounts of data to multiple threads at once.
140 Use memory slab blocks when sending large amounts of data from one thread
14 amounts of memory (as little as 2 KB!) or with simple multi-threading
320 on one object each, saving possibly large amounts of stack space.
78 Systems with very large amounts of memory (such as 512M or more)
98 the runtime of the ISR whenever large amounts of data are received,
142 SD card used to store large amounts of data.
469 * to wait multiple events, sleep smaller amounts of data. in net_config_init_by_iface()
538 * (adx345_stram - line 203), using smaller amounts of samples
402 [Large amounts of debug output]
464 /* At this point the call amounts to (part of) an in ieee802154_recv()
588 # never-ending amounts of special case code here to skip special
607 be helpful to quickly reformat large amounts of new source code to our
