Jeff, I will address all of your points in my next post.
> 5) What is the point of using the hardware semaphore? Is a firmware > competing with the device driver somehow, and its activities require > synchronization with the OS driver? >From the body of my previous post: - ql_wait_for_drvr_lock is used to protect resources that are shared across the network and iSCSI functions. This protection is mostly during chip initialization and resets, but also include link management. The drvr_lock is to allow the iSCSI driver, iSCSI firmware, and the network driver exclusive access to common points in the hardware. > 12) For new drivers, we see additional work and little value for > maintained #ifdef'd NAPI and non-NAPI code paths. Just pick the best > one (and justify that decision with sound technical rationale). I am not sure what sound technical rationale would apply here. NAPI has better thoughput and non-NAPI has lower latency. However, I will pick one and remove the other. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
