On Fri, 2014-09-26 at 10:20 +0200, Hannes Reinecke wrote: > On 09/26/2014 10:03 AM, Christoph Hellwig wrote: > > On Fri, Sep 26, 2014 at 08:29:29AM +0200, Hannes Reinecke wrote: > >> Hi Christoph, > >> > >> as discussed it would make sense to use the request->tag in eg > >> scmd_printk() to identify the command. > >> Which I duly did, only to figure out that the tag is always '-1', ie > >> tagging is not in use. > >> (Which is okay from the SCSI side, seeing the TCQ is basically a > >> SCSI parallel thing). > > > > tag are still a live part of SAM for every transport, they've only > > been renamed to "command identifier" in SAM-4 to confuse everyone. > > > >> Looking closer I found plenty of code for handling tags in the block > >> layer (and the blk-mq stuff, of course), but virtually none of the > >> non-SPI driver seems to be using them. > > > > A quick grep for scsi_activate_tcq disagrees with you. > > > Yeah, I've noticed after I've written the mail. > However, main point still stands: using 'tag' to identify commands > is pointless if not all of the LLDDs use tagging ... Every non parallel LLD uses tagging; they all use the network request response model, so they can no longer hold the bus until they get an answer (which was how untagged commands work in SPI), so for most of the transports, untagged commands aren't legal. Of course, some drivers roll their own tags instead of using the block ones. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
