Struct io_uring::Parameters
source · pub struct Parameters(_);Expand description
The parameters that were used to construct an IoUring.
Implementations§
source§impl Parameters
impl Parameters
sourcepub fn is_setup_sqpoll(&self) -> bool
pub fn is_setup_sqpoll(&self) -> bool
Whether a kernel thread is performing queue polling. Enabled with Builder::setup_sqpoll.
Examples found in repository?
478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
f.debug_struct("Parameters")
.field("is_setup_sqpoll", &self.is_setup_sqpoll())
.field("is_setup_iopoll", &self.is_setup_iopoll())
.field("is_feature_single_mmap", &self.is_feature_single_mmap())
.field("is_feature_nodrop", &self.is_feature_nodrop())
.field("is_feature_submit_stable", &self.is_feature_submit_stable())
.field("is_feature_rw_cur_pos", &self.is_feature_rw_cur_pos())
.field(
"is_feature_cur_personality",
&self.is_feature_cur_personality(),
)
.field("is_feature_poll_32bits", &self.is_feature_poll_32bits())
.field("sq_entries", &self.0.sq_entries)
.field("cq_entries", &self.0.cq_entries)
.finish()
}More examples
113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162
pub fn submit_and_wait(&self, want: usize) -> io::Result<usize> {
let len = self.sq_len();
let mut flags = 0;
// This logic suffers from the fact the sq_cq_overflow and sq_need_wakeup
// each cause an atomic load of the same variable, self.sq_flags.
// In the hottest paths, when a server is running with sqpoll,
// this is going to be hit twice, when once would be sufficient.
if want > 0 || self.params.is_setup_iopoll() || self.sq_cq_overflow() {
flags |= sys::IORING_ENTER_GETEVENTS;
}
if self.params.is_setup_sqpoll() {
if self.sq_need_wakeup() {
flags |= sys::IORING_ENTER_SQ_WAKEUP;
} else if want == 0 {
// The kernel thread is polling and hasn't fallen asleep, so we don't need to tell
// it to process events or wake it up
return Ok(len);
}
}
unsafe { self.enter::<libc::sigset_t>(len as _, want as _, flags, None) }
}
pub fn submit_with_args(
&self,
want: usize,
args: &types::SubmitArgs<'_, '_>,
) -> io::Result<usize> {
let len = self.sq_len();
let mut flags = sys::IORING_ENTER_EXT_ARG;
if want > 0 {
flags |= sys::IORING_ENTER_GETEVENTS;
}
if self.params.is_setup_sqpoll() {
if self.sq_need_wakeup() {
flags |= sys::IORING_ENTER_SQ_WAKEUP;
} else if want == 0 {
// The kernel thread is polling and hasn't fallen asleep, so we don't need to tell
// it to process events or wake it up
return Ok(len);
}
}
unsafe { self.enter(len as _, want as _, flags, Some(&args.args)) }
}sourcepub fn is_setup_iopoll(&self) -> bool
pub fn is_setup_iopoll(&self) -> bool
Whether waiting for completion events is done with a busy loop instead of using IRQs.
Enabled with Builder::setup_iopoll.
Examples found in repository?
478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
f.debug_struct("Parameters")
.field("is_setup_sqpoll", &self.is_setup_sqpoll())
.field("is_setup_iopoll", &self.is_setup_iopoll())
.field("is_feature_single_mmap", &self.is_feature_single_mmap())
.field("is_feature_nodrop", &self.is_feature_nodrop())
.field("is_feature_submit_stable", &self.is_feature_submit_stable())
.field("is_feature_rw_cur_pos", &self.is_feature_rw_cur_pos())
.field(
"is_feature_cur_personality",
&self.is_feature_cur_personality(),
)
.field("is_feature_poll_32bits", &self.is_feature_poll_32bits())
.field("sq_entries", &self.0.sq_entries)
.field("cq_entries", &self.0.cq_entries)
.finish()
}More examples
113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137
pub fn submit_and_wait(&self, want: usize) -> io::Result<usize> {
let len = self.sq_len();
let mut flags = 0;
// This logic suffers from the fact the sq_cq_overflow and sq_need_wakeup
// each cause an atomic load of the same variable, self.sq_flags.
// In the hottest paths, when a server is running with sqpoll,
// this is going to be hit twice, when once would be sufficient.
if want > 0 || self.params.is_setup_iopoll() || self.sq_cq_overflow() {
flags |= sys::IORING_ENTER_GETEVENTS;
}
if self.params.is_setup_sqpoll() {
if self.sq_need_wakeup() {
flags |= sys::IORING_ENTER_SQ_WAKEUP;
} else if want == 0 {
// The kernel thread is polling and hasn't fallen asleep, so we don't need to tell
// it to process events or wake it up
return Ok(len);
}
}
unsafe { self.enter::<libc::sigset_t>(len as _, want as _, flags, None) }
}sourcepub fn is_feature_single_mmap(&self) -> bool
pub fn is_feature_single_mmap(&self) -> bool
If this flag is set, the SQ and CQ rings were mapped with a single mmap(2) call. This
means that only two syscalls were used instead of three.
Examples found in repository?
478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
f.debug_struct("Parameters")
.field("is_setup_sqpoll", &self.is_setup_sqpoll())
.field("is_setup_iopoll", &self.is_setup_iopoll())
.field("is_feature_single_mmap", &self.is_feature_single_mmap())
.field("is_feature_nodrop", &self.is_feature_nodrop())
.field("is_feature_submit_stable", &self.is_feature_submit_stable())
.field("is_feature_rw_cur_pos", &self.is_feature_rw_cur_pos())
.field(
"is_feature_cur_personality",
&self.is_feature_cur_personality(),
)
.field("is_feature_poll_32bits", &self.is_feature_poll_32bits())
.field("sq_entries", &self.0.sq_entries)
.field("cq_entries", &self.0.cq_entries)
.finish()
}sourcepub fn is_feature_nodrop(&self) -> bool
pub fn is_feature_nodrop(&self) -> bool
If this flag is set, io_uring supports never dropping completion events. If a completion event occurs and the CQ ring is full, the kernel stores the event internally until such a time that the CQ ring has room for more entries.
Examples found in repository?
478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
f.debug_struct("Parameters")
.field("is_setup_sqpoll", &self.is_setup_sqpoll())
.field("is_setup_iopoll", &self.is_setup_iopoll())
.field("is_feature_single_mmap", &self.is_feature_single_mmap())
.field("is_feature_nodrop", &self.is_feature_nodrop())
.field("is_feature_submit_stable", &self.is_feature_submit_stable())
.field("is_feature_rw_cur_pos", &self.is_feature_rw_cur_pos())
.field(
"is_feature_cur_personality",
&self.is_feature_cur_personality(),
)
.field("is_feature_poll_32bits", &self.is_feature_poll_32bits())
.field("sq_entries", &self.0.sq_entries)
.field("cq_entries", &self.0.cq_entries)
.finish()
}sourcepub fn is_feature_submit_stable(&self) -> bool
pub fn is_feature_submit_stable(&self) -> bool
If this flag is set, applications can be certain that any data for async offload has been consumed when the kernel has consumed the SQE.
Examples found in repository?
478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
f.debug_struct("Parameters")
.field("is_setup_sqpoll", &self.is_setup_sqpoll())
.field("is_setup_iopoll", &self.is_setup_iopoll())
.field("is_feature_single_mmap", &self.is_feature_single_mmap())
.field("is_feature_nodrop", &self.is_feature_nodrop())
.field("is_feature_submit_stable", &self.is_feature_submit_stable())
.field("is_feature_rw_cur_pos", &self.is_feature_rw_cur_pos())
.field(
"is_feature_cur_personality",
&self.is_feature_cur_personality(),
)
.field("is_feature_poll_32bits", &self.is_feature_poll_32bits())
.field("sq_entries", &self.0.sq_entries)
.field("cq_entries", &self.0.cq_entries)
.finish()
}sourcepub fn is_feature_rw_cur_pos(&self) -> bool
pub fn is_feature_rw_cur_pos(&self) -> bool
If this flag is set, applications can specify offset == -1 with Readv,
Writev, ReadFixed,
WriteFixed, Read and Write,
which behaves exactly like setting offset == -1 in preadv2(2) and pwritev2(2): it’ll use
(and update) the current file position.
This obviously comes with the caveat that if the application has multiple reads or writes in flight, then the end result will not be as expected. This is similar to threads sharing a file descriptor and doing IO using the current file position.
Examples found in repository?
478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
f.debug_struct("Parameters")
.field("is_setup_sqpoll", &self.is_setup_sqpoll())
.field("is_setup_iopoll", &self.is_setup_iopoll())
.field("is_feature_single_mmap", &self.is_feature_single_mmap())
.field("is_feature_nodrop", &self.is_feature_nodrop())
.field("is_feature_submit_stable", &self.is_feature_submit_stable())
.field("is_feature_rw_cur_pos", &self.is_feature_rw_cur_pos())
.field(
"is_feature_cur_personality",
&self.is_feature_cur_personality(),
)
.field("is_feature_poll_32bits", &self.is_feature_poll_32bits())
.field("sq_entries", &self.0.sq_entries)
.field("cq_entries", &self.0.cq_entries)
.finish()
}sourcepub fn is_feature_cur_personality(&self) -> bool
pub fn is_feature_cur_personality(&self) -> bool
If this flag is set, then io_uring guarantees that both sync and async execution of
a request assumes the credentials of the task that called Submitter::enter to queue the requests.
If this flag isn’t set, then requests are issued with the credentials of the task that originally registered the io_uring.
If only one task is using a ring, then this flag doesn’t matter as the credentials will always be the same.
Note that this is the default behavior, tasks can still register different personalities
through Submitter::register_personality.
Examples found in repository?
478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
f.debug_struct("Parameters")
.field("is_setup_sqpoll", &self.is_setup_sqpoll())
.field("is_setup_iopoll", &self.is_setup_iopoll())
.field("is_feature_single_mmap", &self.is_feature_single_mmap())
.field("is_feature_nodrop", &self.is_feature_nodrop())
.field("is_feature_submit_stable", &self.is_feature_submit_stable())
.field("is_feature_rw_cur_pos", &self.is_feature_rw_cur_pos())
.field(
"is_feature_cur_personality",
&self.is_feature_cur_personality(),
)
.field("is_feature_poll_32bits", &self.is_feature_poll_32bits())
.field("sq_entries", &self.0.sq_entries)
.field("cq_entries", &self.0.cq_entries)
.finish()
}sourcepub fn is_feature_fast_poll(&self) -> bool
pub fn is_feature_fast_poll(&self) -> bool
Whether async pollable I/O is fast.
See the commit message that introduced it for more details.
sourcepub fn is_feature_poll_32bits(&self) -> bool
pub fn is_feature_poll_32bits(&self) -> bool
Whether poll events are stored using 32 bits instead of 16. This allows the user to use
EPOLLEXCLUSIVE.
Examples found in repository?
478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
f.debug_struct("Parameters")
.field("is_setup_sqpoll", &self.is_setup_sqpoll())
.field("is_setup_iopoll", &self.is_setup_iopoll())
.field("is_feature_single_mmap", &self.is_feature_single_mmap())
.field("is_feature_nodrop", &self.is_feature_nodrop())
.field("is_feature_submit_stable", &self.is_feature_submit_stable())
.field("is_feature_rw_cur_pos", &self.is_feature_rw_cur_pos())
.field(
"is_feature_cur_personality",
&self.is_feature_cur_personality(),
)
.field("is_feature_poll_32bits", &self.is_feature_poll_32bits())
.field("sq_entries", &self.0.sq_entries)
.field("cq_entries", &self.0.cq_entries)
.finish()
}pub fn is_feature_sqpoll_nonfixed(&self) -> bool
pub fn is_feature_ext_arg(&self) -> bool
pub fn is_feature_native_workers(&self) -> bool
sourcepub fn sq_entries(&self) -> u32
pub fn sq_entries(&self) -> u32
The number of submission queue entries allocated.
sourcepub fn cq_entries(&self) -> u32
pub fn cq_entries(&self) -> u32
The number of completion queue entries allocated.
Trait Implementations§
source§impl Clone for Parameters
impl Clone for Parameters
source§fn clone(&self) -> Parameters
fn clone(&self) -> Parameters
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more