Linus> which instead of using a read-modify-write cycle and a long
Linus> immediate just uses a single write-cycle. It makes gcc allocate
Linus> a word on the stack, and sometimes that might be unnecessary,
Linus> but it should be smaller and faster. You might want to check
Linus> out code generation..
This can actually become a bit expensive if you use mb() a lot in your
code, ie. if you use __raw_writel() etc.
Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/