linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Theodore Tso <tytso@mit.edu>, Paul Mackerras <paulus@samba.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jeff Garzik <jeff@garzik.org>,
	linux-kernel@vger.kernel.org, Amit Arora <aarora@in.ibm.com>,
	Andi Kleen <ak@suse.de>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Arnd Bergmann <arnd@arndb.de>, "Luck, Tony" <tony.luck@intel.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Mark Fasheh <mark.fasheh@oracle.com>,
	linux-arch@vger.kernel.org
Subject: Re: fallocate-implementation-on-i86-x86_64-and-powerpc.patch
Date: Wed, 11 Jul 2007 20:47:01 +0200	[thread overview]
Message-ID: <20070711184701.GA9035@osiris.ibm.com> (raw)
In-Reply-To: <20070711153939.GA19456@thunk.org>

On Wed, Jul 11, 2007 at 11:39:39AM -0400, Theodore Tso wrote:
> On Wed, Jul 11, 2007 at 10:50:49AM +1000, Paul Mackerras wrote:
> > > On Wed, 11 Jul 2007 09:27:40 +1000
> > > Paul Mackerras <paulus@samba.org> wrote:
> > > 
> > > > We did come up with an order that worked for everybody, but that
> > > > discussion seemed to get totally ignored by the ext4 developers.
> 
> Well, in the end it was a toss-up between
> 
> asmlinkage long sys_fallocate(int fd, int mode, loff_t offset, loff_t len)
> 
> and 
> 
> asmlinkage long sys_fallocate(loff_t offset, loff_t len, int fd, int mode)
> 
> There were a number of folks who preferred having int fd first, and I
> *thought* Amit had gotten agreement from either Martin or Heiko that
> it was ok to do this as an exception, even though it was extra work
> for that arch.  But if not, we can try going back the second
> alternative, or even the 6 32-bits args (off_high, off_low, len_high,
> len_low) approach, but I think that drew even more fire. 

The second approach would work for all architectures..  but some people
didn't like (no technical reason) not having fd as first argument.

Just go ahead with the current approach. s390 seems to be the only
architecture which suffers from this and I wouldn't like to start this
discussion again.

  reply	other threads:[~2007-07-11 18:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070710013152.ef2cd200.akpm@linux-foundation.org>
     [not found] ` <20070710115251.GG2343@thunk.org>
     [not found]   ` <20070710101558.cea7aab1.akpm@linux-foundation.org>
2007-07-10 17:44     ` fallocate-implementation-on-i86-x86_64-and-powerpc.patch Jeff Garzik
2007-07-10 23:27       ` fallocate-implementation-on-i86-x86_64-and-powerpc.patch Paul Mackerras
2007-07-11  0:16         ` fallocate-implementation-on-i86-x86_64-and-powerpc.patch Andrew Morton
2007-07-11  0:50           ` fallocate-implementation-on-i86-x86_64-and-powerpc.patch Paul Mackerras
2007-07-11 15:39             ` fallocate-implementation-on-i86-x86_64-and-powerpc.patch Theodore Tso
2007-07-11 18:47               ` Heiko Carstens [this message]
2007-07-11 20:32                 ` fallocate-implementation-on-i86-x86_64-and-powerpc.patch Martin Schwidefsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070711184701.GA9035@osiris.ibm.com \
    --to=heiko.carstens@de.ibm.com \
    --cc=aarora@in.ibm.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=jeff@garzik.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.fasheh@oracle.com \
    --cc=paulus@samba.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tony.luck@intel.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).