On 2/28/2017 8:34 AM, Hannes Reinecke wrote:
Can you clarify these? Are these 'just' resource allocation problems or something else, too?
Most are resource allocation - buffer pools, dma pools, pages for resources, and hw resource allocation splits. However, async receive RQ policies are a case where initiator and target have to share the policy and perhaps a buffer pool, so they have to be careful. Another area is in ABTS handling. Initiators typically leave things up to the hardware, and do little if any ABTS handling. Most targets though, as CMD IU may be received without an assign exchange context and be buffered until the target is ready to do something, require that they handle ABTS's. Some of the target features, when enabled, dictate host ownership of ABTS policy. So, if running I+T, it gets rather tricky.
-- james
