Re: f_ops flag to speed up compatible ioctls in linux kernel

[Olivier Galibert]

On Wed, Sep 01, 2004 at 04:16:59AM -0600, filia@xxxxxxxxxxxx wrote:
> I do not see much point in renaming ioctl() to write() all over the place - 
> at least when people see ioctl() they understand that it is not standard 
> functionality. write() will for sure confuse a lot of people. 

Because you can encapsulate write while you can't encapsulate ioctl
for a start.  And because ascii is good and opaque binary is bad.  You
don't change the target position of your motion device millions of
time per second.  You can easily send your commands and replies
(you're allowed read, too) as text, and immediatly you make logging,
debugging and reproducing actions way easier.  Plus API portability to
64bits/other endian is free.

  OG.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/