rtio: Enable submit/consume semaphores by default
The default behavior for thread pending of completions should use semaphores rather than yield/wait looping when multithreading is available. Disable by default only when multithreading isn't available. Signed-off-by: Tom Burdick <thomas.burdick@intel.com>
This commit is contained in:
parent
f4a7d24858
commit
71bf36387c
|
@ -8,14 +8,20 @@ if RTIO
|
|||
|
||||
config RTIO_SUBMIT_SEM
|
||||
bool "Use a semaphore when waiting for completions in rtio_submit"
|
||||
default n if !MULTITHREADING
|
||||
default y
|
||||
help
|
||||
When calling rtio_submit a semaphore is available to sleep the calling
|
||||
thread for each completion queue event until the wait count is met. This
|
||||
adds a small RAM overhead for a single semaphore. By default wait_for will
|
||||
use polling on the completion queue with a k_yield() in between iterations.
|
||||
|
||||
Enabled by default unless !MULTITHREADING
|
||||
|
||||
config RTIO_CONSUME_SEM
|
||||
bool "Use a semaphore when waiting for completions in rtio_cqe_consume_block"
|
||||
default n if !MULTITHREADING
|
||||
default y
|
||||
help
|
||||
When calling rtio_cqe_consume_block a semaphore is available to sleep the
|
||||
calling thread for each completion queue event until the wait count is met.
|
||||
|
@ -23,6 +29,8 @@ config RTIO_CONSUME_SEM
|
|||
will use polling on the completion queue with a k_yield() in between
|
||||
iterations.
|
||||
|
||||
Enabled by default unless !MULTIHREADING
|
||||
|
||||
config RTIO_SYS_MEM_BLOCKS
|
||||
bool "Include system memory blocks as an optional backing read memory pool"
|
||||
select SYS_MEM_BLOCKS
|
||||
|
|
Loading…
Reference in New Issue