3D Textures -- xyz@CPU becomes zyx@GPU Is this the normal behaviour?

Probably row major order versus column major order. I have only ever used 3D textures with a code with column major ordered storage, and it just worked, but I have no proof that it is really ordering that is in play here. The 3D texture documentation is rather, err scant…