Jeff Garzik <jgarzik@pobox.com> writes: > > ioctl's are a pain for 32->64-bit translation layers. Using a > read/write interface allows one to create an interface that requires > no translation layer -- a big deal for AMD64 and IA32e processors > moving forward -- and it also gives one a lot more control over the > interface. Sorry, Jeff, but that's just not true. While ioctls need an additional entry in the conversion table, they can at least easily get an translation handler if needed. When they are correctly designed you just need a single line to enable pass through the emulation. If you don't want to add that line to the generic compat_ioctl.h file you can also do it in your driver. read/write has the big disadvantage that if someone gets the emulation wrong (and that happens regularly) it is near impossible to add an emulation handler then, because there is no good way to hook into the read/write paths. There may be valid reasons to go for read/write, but 32bit emulation is not one of them. In fact from the emulation perspective read/write should be avoided. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
