Jesse Brandeburg 945a51517c intel drivers: repair missing flush operations ... after review of all intel drivers, found several instances where drivers had the incorrect pattern of: memory mapped write(); delay(); which should always be: memory mapped write(); write flush(); /* aka memory mapped read */ delay(); explanation: The reason for including the flush is that writes can be held (posted) in PCI/PCIe bridges, but the read always has to complete synchronously and therefore has to flush all pending writes to a device. If a write is held and followed by a delay, the delay means nothing because the write may not have reached hardware (maybe even not until the next read) Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com> Tested-by: Aaron Brown <aaron.f.brown@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>		2011-08-04 04:59:07 -07:00
..
defines.h
ethtool.c	igbvf: remove bogus phys_id	2011-05-04 12:12:22 -07:00
igbvf.h	igbvf: do vlan cleanup	2011-07-21 13:47:55 -07:00
Makefile
mbx.c
mbx.h
netdev.c	intel drivers: repair missing flush operations	2011-08-04 04:59:07 -07:00
regs.h
vf.c
vf.h