On Fri, May 11 2007, Vasily Tarasov wrote: > Hello all, > > The function blk_start_queueing() calls __generic_unplug_device() > function directly without tracing BLK_TA_UNPLUG_IO action. So I have an > odd output of blktrace, when requests go through the plugged queue. I > suppose it's a BUG, or do I miss something?
The unplug trace is meant to log upper layers doing an unplug to start IO, not internal use that wants to kick the queue for whatever reasons. We could log those as well, but it would be preferential to seperate them. blk_start_queuing() is one such call, for instance. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-btrace" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
