FUJITA Tomonori wrote: > If we want to make swiotlb generic (make on any architectures), we > need to handle more cache issues here, I think. So it's better to have > more generic ways instead of adding hooks to some archs. > Ok. So what would be an acceptable way of handling this in a generic way? Should we for example have 2 levels of DMA ops in the swiotlb case (swiotlb and "actual") and call the 2nd level ("actual") from the swiotlb code whenever we need to act on non-bounced buffers? Any other ideas? Thanks, Albert -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
![]() |