Thread (283 messages) flat view 283 messages, 37 authors, 2007-07-12

Re: Interface for the new fallocate() system call

From: Heiko Carstens <hidden>
Date: 2007-03-30 07:19:29
Also in: linux-fsdevel, linux-xfs, lkml

quoted
Even ARM prefers above kind of layout. For details please see the
definition of sys_arm_sync_file_range().
This is a clean-looking option.  Can s390 be changed to support seven-arg
syscalls?
quoted
Option of loff_t => high u32 + low u32
--------------------------------------
Matthew and Russell have suggested another option of breaking each
"loff_t" into two "u32"s. This will result in 6 arguments in total.

Following think that this is a good alternative:
Matthew Wilcox, Russell King, Heiko Carstens

Following do not like this idea:
Chris Wedgwood
It's a bit weird-looking, but the six-32-bit-args approach is simple
enought to understand and implement.  Presumably the glibc wrapper
would hide that detail from everyone.
s390 can be changed to support seven-arg syscalls. But that would require
creating an additional stackframe in *libc to save original register
contents and in addition it would make our syscall hotpath slower.
That is because we have to take care of an additional register that might
contain user space passed contents and needs to be put on the kernel stack.
If possible I'd prefer the six-32-bit-args approach.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help