Prev: swiotlb: Make swiotlb bookkeeping functions visible in the header file.
Next: 2.6.34-rc1 to -rc3 on zaurus: no longer boots
From: Konrad Rzeszutek Wilk on 7 Apr 2010 15:40
> > Since the last posting I've:
> > - Made the exported functions/variables have the 'swiotlb_bk' prefix instead
> > of the 'do_[map|unmap]*' and 'io_tlb_*' combination.
> Why can't we use more simpler names such as 'swiotlb_tbl_index'?
Much better. I was trying to come up with a name and the one I came up
with was 'bookkeeping', which I shortned to 'bk'. But 'tbl'
> Why do we need to add the prefix to static things like
> 'swiotlb_bk_list', 'swiotlb_bk_index', etc? Please let them alone.
> > I had not addressed the question of removing the 'overflow' buffer. There are over
> > ~300 instances of the the DMA operations not being checked which plan on addressing
> > in a seperate set of patches that will slowly roll out the checks and then
> > finally the removal of the 'overflow' buffer.
> Except for swiotlb, no IOMMU implementations has the mechanism of
I believe the GART one does it too. I think the overflow points to the
first page of the GART address and has logic to remind the user that danger
> overflow buffer. So drivers that don't check a DMA mapping error are
> broken anyway. Also the size of the overflow is 32K by default. We
> often see larger request than that. Even with the overflow mechanism,
> we see data corruption anyway.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/