Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268204AbUIGPBn (ORCPT ); Tue, 7 Sep 2004 11:01:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268175AbUIGOtj (ORCPT ); Tue, 7 Sep 2004 10:49:39 -0400 Received: from mail.mellanox.co.il ([194.90.237.34]:25700 "EHLO mtlex01.yok.mtl.com") by vger.kernel.org with ESMTP id S268170AbUIGOrJ (ORCPT ); Tue, 7 Sep 2004 10:47:09 -0400 Date: Tue, 7 Sep 2004 17:45:43 +0300 From: "Michael S. Tsirkin" To: Andi Kleen Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org Subject: Re: [discuss] f_ops flag to speed up compatible ioctls in linux kernel Message-ID: <20040907144543.GA1340@mellanox.co.il> Reply-To: "Michael S. Tsirkin" References: <20040901072245.GF13749@mellanox.co.il> <20040903080058.GB2402@wotan.suse.de> <20040907104017.GB10096@mellanox.co.il> <20040907121418.GC25051@wotan.suse.de> <20040907134517.GA1016@mellanox.co.il> <20040907141524.GA13862@wotan.suse.de> <20040907142530.GB1016@mellanox.co.il> <20040907142945.GB20981@wotan.suse.de> <20040907143702.GC1016@mellanox.co.il> <20040907144452.GC20981@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040907144452.GC20981@wotan.suse.de> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1341 Lines: 33 Hello! Quoting r. Andi Kleen (ak@suse.de) "Re: [discuss] f_ops flag to speed up compatible ioctls in linux kernel": > On Tue, Sep 07, 2004 at 05:37:02PM +0300, Michael S. Tsirkin wrote: > > Hello! > > Quoting r. Andi Kleen (ak@suse.de) "Re: [discuss] f_ops flag to speed up compatible ioctls in linux kernel": > > > On Tue, Sep 07, 2004 at 05:25:30PM +0300, Michael S. Tsirkin wrote: > > > > > It may help your module, but won't solve the general problem shorter > > > > > term. > > > > But longer term it will be better, so why not go there? > > > > Once the infrastructure is there, drivers will be able to be > > > > migrated as required. > > > > > > I have no problems with that. You would need two new entry points: > > > one 64bit one without BKL and a 32bit one also without BKL. > > > > > > I think there were some objections to this scheme in the past, > > > but I cannot think of a good alternative. > > > > > > > Maybe one entry point with a flag? > > That would be IMHO far uglier than two. > > -Andi > What would be a good name? ioctl32/ioctl64? ioctl_compat/ioctl_native? - 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/