On Wed, Jun 15, 2011 at 09:58:41AM -0700, Nicholas A. Bellinger wrote: > > It currently is, but I think we'd better be off stopping to call it from > > IRQ context. Soon after we offload the work to thread context anyway. > > By moving the point of offloading a little earlier we can simply the > > calling conventions a lot, and keep the amount of code that needs > > IRQ-safe locking minimal. > > > > The thing here is that the new descriptor can't be offloaded into thread > context for TFO->new_cmd_map() processing until the se_cmd->se_dev > assignment has occured, because we don't know which backend it's > destined for. The actual backend is pretty irrelevant. What matters with the current code is which se_dev it is for, but once switched to the concurrency managed workqueues that becomes irrelevant, too. -- 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
