On 8/11/2016 2:22 PM, Christoph Hellwig wrote:
+ queue->work_q = alloc_workqueue("ntfc%d.%d.%d", 0, 0,
+ assoc->tgtport->fc_target_port.port_num,
+ assoc->a_id, qid);
Do we really need a workqueue per queue?
I thought we did - so there was always an execution context for the
nvmet layer when a command is received. My understanding was the nvmet
layer processes the cmd synchronously. I avoided per cpu - as I assumed
the synchronous flows would end up blocking other connections to other
subsystems/controllers.
If that's not the case - can you describe the nvmet layer better so I
understand what we need ?
No reference counting?
yes - will make a pass at it.
-- james
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html