> I'm not sure that can work either. The PCI-X spec is very clear, you
> must wait for a non-posted completion if you care about order. Doing a
> config read in the driver as a surrogate flush is not good enough in
> the general case. Like you say, a pci bridge is free to reorder all
> in flight non-posted operations.
No, hang on. Nothing can reorder a dependent read to start after a
write that it depends on, can it? So a config read of PCI_COMMAND
can't start until the completion of a config write of the same
register, right?
- R.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
