> Feedback appreciated. I still hope to get this started as a PSARC case > *really* soon.
What's the rush? 8-) It seems like the block device driver (the nvflash driver or its equivalent -- there should probably be some sort of catchy acronym for this) would want to register the maximum number of commands it can handle at one time, so that the framework can handle the queuing. If the block device driver sets B2S_TARGET_FLAG_HOTPLUGGABLE and a new device gets plugged in, somehow it needs to call b2s_alloc_target() and b2s_register_target(). How does it do that? How does blk2scsa timeout or cancel submitted commands? Does the FORMAT command allow a certain blocksize to be specified? It seems like the framework could keep track of the fact that a FORMAT command is outstanding so that the reserve/release pseudo-commands aren't needed. If that's true, it would also remove the need for the B2S_EFORMATTING return code. Same goes for the START/STOP unit command and B2S_ESTOPPED/ B2S_ESTARTING. The name B2S_EBADMSG may be confused with a parallel SCSI error. When would a block driver return B2S_EPARM vs B2S_EINVAL? You mean "b2s request" rather than "SCSI packet," right? - Eric This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
