Prev: [054/140] drm/radeon/kms: CS checker texture fixes for r1xx/r2xx/r3xx
Next: [076/140] genirq: Deal with desc->set_type() changing desc->chip
From: Chris Friesen on 30 Jul 2010 14:50

Documentation/DMA-API-HOWTO.txt says that memory barriers are still
required when accessing consistent mappings. The example they give is
for reordering stores to consistent memory but I assume this also
applies to reordering loads.

However, I see many net drivers accessing the descriptor ring (in
consistent memory), checking the status bit for the buffer, then calling
dma_unmap_single() and accessing the data without any explicit memory
barrier. Does the unmapping call act as a barrier in this case?

Thanks,

Chris

--
Chris Friesen
Software Developer
GENBAND
chris.friesen(a)genband.com
www.genband.com
--
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/
 | 
Pages: 1
Prev: [054/140] drm/radeon/kms: CS checker texture fixes for r1xx/r2xx/r3xx
Next: [076/140] genirq: Deal with desc->set_type() changing desc->chip