Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751906AbXB0VhF (ORCPT ); Tue, 27 Feb 2007 16:37:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751909AbXB0VhF (ORCPT ); Tue, 27 Feb 2007 16:37:05 -0500 Received: from smtp.osdl.org ([65.172.181.24]:53221 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751908AbXB0VhD (ORCPT ); Tue, 27 Feb 2007 16:37:03 -0500 Date: Tue, 27 Feb 2007 13:36:56 -0800 From: Andrew Morton To: Stephen Hemminger Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH] udivdi3: 64 bit divide Message-Id: <20070227133656.c452fbb4.akpm@linux-foundation.org> In-Reply-To: <20070227131840.672d6932@localhost> References: <20070226173517.66bf0fec@freekitty> <20070227122437.da27c3cd.akpm@linux-foundation.org> <20070227131840.672d6932@localhost> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.19; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1630 Lines: 36 > On Tue, 27 Feb 2007 13:18:40 -0800 Stephen Hemminger wrote: > On Tue, 27 Feb 2007 12:24:37 -0800 > Andrew Morton wrote: > > > > On Mon, 26 Feb 2007 17:35:17 -0800 Stephen Hemminger wrote: > > > The kernel already has several implmentations and usages of 64 by 64 > > > bit divide. > > > > > > Although it is significantly slower, there are places that need it so > > > provide one generic version using scaling, and allow existing platform > > > versions to continue. > > > > The reason we implement 64/32 via do_div() is, for better or for worse, to > > make people think before they use it. And to make it stand out, and so > > that we discover places that are using it by accident, where they could use > > something cheaper. > > > > However your implementation of the presumably even more expensive 64/64 > > allows us to do 64/64 with a plain old "/" operator. > > > > If the do_div() philosophy is any good then we should surely repeat it for > > 64/64, no? > > > > Then we should pull the existing udivdi3 implementations? Not much point really. Some architectures have gone and done that, but x86 has not. x86 has enough coverage for us to pick up most problems, and any remaining problems are obviously in scruffy architectures which don't care about performance ;) - 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/