1. Unified SG segment allocation. The SCSI layer currently has a
mempool implementation to cope with this, is there a reason it can't
become block generic?
2. Device locality awareness. Quite a bit of the esoteric SCSI queueing
code occurs because we have two type of queue events:
a. device can't accept another command---stop queue and restart when the
device sends a completion back
b. the host adapter is out of resources for *all* its devices. Block
all device queues until we free some resources (again, usually a
returning command).
3. Perhaps some type of unified command handling. At the moment, we all
seem to allocate DMA'able regions for our commands/taskfiles/whatever
and attach them to reqest->special. Then we need to release them again
before completing the request.
4. Same thing goes for sense buffers.
5. There needs to be some amalgam of the SCSI code for dynamic tag
command queue depth handling.
OK, I'll stop now.
James
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/