From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org ([203.10.76.45]:36077 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751119AbXGJX1q (ORCPT ); Tue, 10 Jul 2007 19:27:46 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18068.5612.100418.782729@cargo.ozlabs.ibm.com> Date: Wed, 11 Jul 2007 09:27:40 +1000 From: Paul Mackerras Subject: Re: fallocate-implementation-on-i86-x86_64-and-powerpc.patch In-Reply-To: <4693C580.2000506@garzik.org> References: <20070710013152.ef2cd200.akpm@linux-foundation.org> <20070710115251.GG2343@thunk.org> <20070710101558.cea7aab1.akpm@linux-foundation.org> <4693C580.2000506@garzik.org> Sender: linux-arch-owner@vger.kernel.org To: Jeff Garzik Cc: Andrew Morton , Theodore Tso , linux-kernel@vger.kernel.org, Amit Arora , Andi Kleen , Benjamin Herrenschmidt , Arnd Bergmann , "Luck, Tony" , Heiko Carstens , Martin Schwidefsky , Mark Fasheh , linux-arch@vger.kernel.org List-ID: Jeff Garzik writes: > Andrew Morton wrote: > > So I dropped everything. Let's start again from scratch. I'd suggest that > > for now we go with just an i386/x86_64 implementation, let the arch > > maintainers wire things up when that has settled down. > > > It's my observation that that plan usually works the best. Arch ... except when the initial implementer picks an argument order which doesn't work on some archs, as happened with sys_sync_file_range. That is also the case with fallocate IIRC. We did come up with an order that worked for everybody, but that discussion seemed to get totally ignored by the ext4 developers. Paul.