Re: [RFC PATCHSET RESEND] ioblame: statistical IO analyzer

[Tejun Heo]

Hello, Namhyung.

On Fri, Jan 06, 2012 at 06:00:04PM +0900, Namhyung Kim wrote:
> BTW, it seems the ioblame based on event tracing feature, so
> couldn't it be implemented in userspace with the help of the
> tracepoints and additional information (e.g. intent, ...) you add?
> The perf can deal with them and extend post-processing capability
> easily, and also might reduce some kernel jobs, I guess.

Yeah, it uses tracepoints to gather information it needs, but
producing relevant information (like the intent id) requires
nontrivial state tracking.  The point where it would make sense to
push to userland is the iolog, where all the relevant information has
been gathered for each IO.  Currently, the export interface there is
pretty dumb and slow.

Hmmm... originally, I had variable length data structure there but now
it's fixed so exposing them using tracepoint shouldn't be too
difficult and could actually be better (previously it didn't really
fit TP and ringbuffer should be used directly).  Yeah, that's a
thought.  Generating a TP event per IO shouldn't be taxing and it
would give much better visibility to userland and we can drop the
whole statics configuration and stuff.  Enticing.  I'll think more
about it.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/