On Thu, Nov 26, 2015 at 05:36:20PM +0000, Robin Murphy wrote:
> On 26/11/15 15:37, Joerg Roedel wrote:
> >When the size is bigger than the mask you can either put a WARN on into
> >and return error (to see if that really happens), or just do multiple
> >smaller allocations that fit into the boundary mask.
>
> That case is actually surprisingly common in at least one situation
> - a typical scatterlist coming in from the SCSI layer seems to have
> a max segment length of 65536, a boundary mask of 0xffff, and a
> short first segment followed by subsequent full segments (I guess
> they are the command buffer and data buffers respectively), meaning
> an alignment bump is needed fairly frequently there.
The boundary_mask is a property of the underlying device, which one is
it with that boundary mask?
> I wanted to avoid multiple allocations for various reasons:
> - iommu_map_sg() only takes a single base IOVA, but it's nice if we
> can make use of it.
> - Some of the "complication" would just be shifted into the unmap
> path, and having to make multiple unmap requests to the IOMMU driver
> increases the number of potentially costly TLB syncs.
Yeah, its a trade-off between wasting iova space and a faster
implementation.
> - It minimises contention in the IOVA allocator, which is
> apparently a real-world problem ;)
Thats why we currently evaluate options to get rid of it completly :)
> - I like to minimise the number of people complaining at me that
> whole scatterlists don't get mapped into contiguous IOVA ranges.
Making that assumption is a bug anyway, this is the simple answer you
can give to anyone complaining.
Joerg
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu
