Christoph Hellwig <hch@xxxxxxxxxxxxx> writes: > On Wed, Nov 09, 2016 at 02:31:30PM -0500, Jeff Moyer wrote: >> bio_endio is still called for request_fn drivers, so you'd see two >> completion events for those drivers if we did that, no? > > We'd see the bio_endio trace in addition to the request one, but > they are at different granularities. Similar to how on the issue side > we have trace_block_bio_queue for each bio, and trace_block_rq_issue > for each request. But on the issue side, we have different trace actions: Q vs. I. On the completion side, we just have C. You'd end up getting two C events for each Q, and that may confuse existing utilities (such as blkparse, btt, iowatcher, fio, etc), not to mention any scripts built around the tracepoints, and any users looking at the raw blkparse output. So, are you suggesting we add another action on the endio side? If so, that's a different patch set. ;-) If you're suggesting this multiple C event thing, I'm not on board with that. Cheers, Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-block" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
