On Thu, Jun 16, 2011 at 12:13:26PM -0700, Andy Grover wrote: > I agree. Also, I don't think there should be a handle_cdb_direct because > I think handle_cdb should call transport_generic_new_cmd, we don't need > a "direct" version. transport_generic_new_cmd should be safe (or made > safe) for calling from interrupt context. There's nothing in it that > demands it be executed in the backstore thread's context, and doing so > just incurs a two context switch latency penalty. I think the whole target context/threading model needs a makeover. As we need to switch to a usermode context for just about any operation we should just declare that any fabrict module must call all entry points from user context. The fabric modules can trivially do that using the concurrency managed workqueues if nessecary. At that point the target core can just go ahead by itself without bothering with context switches, and just using another workqueue where it might need additional concurreny (e.g. executing multiple task is parallel for the file backend) -- 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
