Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267312AbUIANqa (ORCPT ); Wed, 1 Sep 2004 09:46:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267250AbUIANqZ (ORCPT ); Wed, 1 Sep 2004 09:46:25 -0400 Received: from dspnet.fr.eu.org ([62.73.5.179]:11531 "EHLO dspnet.fr.eu.org") by vger.kernel.org with ESMTP id S266568AbUIANnI (ORCPT ); Wed, 1 Sep 2004 09:43:08 -0400 Date: Wed, 1 Sep 2004 15:43:00 +0200 From: Olivier Galibert To: linux-kernel@vger.kernel.org Subject: Re: f_ops flag to speed up compatible ioctls in linux kernel Message-ID: <20040901134300.GA85587@dspnet.fr.eu.org> Mail-Followup-To: Olivier Galibert , linux-kernel@vger.kernel.org References: <20040901095229.GA11908@devserv.devel.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 979 Lines: 19 On Wed, Sep 01, 2004 at 04:16:59AM -0600, filia@softhome.net 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/