Linux 2.6 I/O Scheduler & ASM/Raw

Apologies in advance for the simple question but if a database uses raw or ASM storage, is it bypassing the operating system's I/O layer, or not? For example, should the choice of scheduler (cfq, as, noop, deadline) in the Linux 2.6 affect performance of an ASM or RAW filesystem, or should it not? Likewise, are variables such as the maximum I/O size at an OS level (e.g. 512KB or 1M) and the OS block size (8KB, 16KB, ...) still meaningful with raw filesystems?

I suspect the answer to both questions is "yes" but I'm not sure and haven't seen this spelled out clearly....

Bob

--
http://www.freelists.org/webpage/oracle-l