I agree this is a good thing.
> The bio layer works with
> a nice finite list of generic or per-queue constraints; it doesn't care
> currently what the underlying device or IOMMU does.
I don't agree. This whole discussion revolves around getting BIO code and
IOMMU code to agree on how block merging works for a given platform.
Using a callback into IOMMU code means the BIO truly doesn't have to know.
The platform specific IOMMU could just tell BIO code what it wants to
know (how many SG entries would fit into a limited number of physical
> Putting such a callback in would add this entanglement.
yes, sort of. But I think this entanglement is present even for machines
that don't have an IOMMU because of bounce buffers. But if ia64's swiotlb
would be made generic to cover buffer bouncing....
> It could be that the bio people will be OK with this, and I'm just
> worrying about nothing, but in that case, they need to say so...
Would that be Jens Axboe/Dave Miller/et al?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/