Re: [PATCH] Adding userspace_libaio_reap option

[Jeff Moyer <jmoyer@xxxxxxxxxx>]

Dan Ehrenberg <dehrenberg@xxxxxxxxxx> writes:

> When a single thread is reading from a libaio io_context_t object
> in a non-blocking polling manner (that is, with the minimum number
> of events to return being 0), then it is possible to safely read
> events directly from user-space, taking advantage of the fact that
> the io_context_t object is a pointer to memory with a certain layout.
> This patch adds an option, userspace_libaio_reap, which allows
> reading events in this manner when the libaio engine is used.

I haven't yet tried to poke holes in your code, but I'm pretty sure I
can find some.  I have patches for the kernel and libaio which allow
user-space reaping of events.  Why don't I dust those off and post them,
and then fio won't have to change at all?  That seems like to proper
approach to solving the problem.

Cheers,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html