Struct IOContext 

pub struct IOContext<C: IOCallback, Q, W> { /* private fields */ }

IOContext manages the submission of IO tasks to the underlying driver.

It is generic over the callback type C, the submission queue Q, and the worker type W.

Channel Selection for W (Worker)

When configuring the IOContext with a worker W (usually a channel sender cb_workers), you should choose the crossfire channel type based on your sharing model:

• Shared Worker (Multiple Contexts): If you have multiple IOContext instances sharing the same callback worker, use the IOWorkers struct, or pass crossfire::MTx (from mpsc or mpmc channels) with your custom worker implementation. This allows multiple producers (contexts) to send completion events to a single consumer (worker).

• Single Instance (Dedicated Worker): If you have a single IOContext with its own dedicated callback worker, use crossfire::Tx (from spsc channels). This is more efficient for single-producer scenarios.

• inline callback: If you have a very light callback logic, you can use Inline

Implementations

impl<C: IOCallback, Q, W> IOContext<C, Q, W>

where Q: BlockingRxTrait<IOEvent<C>> + Send + 'static, W: Worker<C> + Send + 'static,

pub fn new( depth: usize, queue: Q, cbs: W, driver_type: Driver, ) -> Result<Arc<Self>, Error>

pub fn get_depth(&self) -> usize

pub fn running_count(&self) -> usize