Thread (7 messages) 7 messages, 6 authors, 2007-07-11

Re: fallocate-implementation-on-i86-x86_64-and-powerpc.patch

From: Heiko Carstens <hidden>
Date: 2007-07-11 18:47:20
Also in: lkml

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:
quoted
quoted
On Wed, 11 Jul 2007 09:27:40 +1000
Paul Mackerras [off-list ref] wrote:
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help