Roland Dreier wrote:
Yes, the point of this verb is that the low-level driver owns the page
list from when the fast register work request is posted until it
completes. This should be explicitly documented somewhere.
OK, got it, so this is different case compared to the SG elements which
are not owned by the driver once the posting call returns.
However the reason for having the low-level driver implement it is so
that all strange device-specific issues can be taken care of in the
driver. For instance mlx4 is going to require that the page list be
aligned to 64 bytes, and will DMA from the memory, so we need to use
dma_alloc_consistent(). On the other hand cxgb3 is just going to copy
in software, so kmalloc is sufficient.
I see. Just wondering, in the mlx4 case, is it a must to use dma
consistent memory allocation or dma mapping would work too?
Or.
Or.
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
