>  eieio: prevent CPU from reordering/collapsing reads/writes to memory.
>         (but otherwise run at full steam!)

Thats what mb() does - its a memory-barrier hence the name - it imposes
strong store ordering properties across it. 

> That's why I added the iobarrier() macros (adding _w/_r/_rw on Alan's
> request) that are only related to IO synchronization within the same
> CPU. Essentially it's just renaming the eieio() macro already used in
> many PPC drivers because it's a bad name; Linux/APUS will be sharing
> drivers with Linux/m68k where eieio isn't such a helpful name.

Yep.

x86 and most other processors dont have the notion of a store barrier and
an i/o barrier beign different

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]