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

Re: Interface for the new fallocate() system call

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

On Thu, Mar 29, 2007 at 07:01:54PM +0200, Jan Engelhardt wrote:
Hi,

On Mar 29 2007 17:21, Amit K. Arora wrote:
quoted
We need to come up with the best possible layout of arguments for the
fallocate() system call. Various architectures have different
requirements for how the arguments should look like. Since the mail
chain has become huge, here is the summary of various inputs received
so far.
quoted
s390 prefers following layout:
  int fallocate(int fd, loff_t offset, loff_t len, int mode)
For details on why and how "int, int, loff_t, loff_t" is a problem on
s390, please see Heiko's mail on 16th March. Here is the link:
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg133595.html
Quoting that...
	|len -> r6 + second halve on stack

Then, is not this a gcc glitch? (IMO, it should put all of "len" on the 
stack)
It _does_ put all of "len" on the stack. That is what I tried to explain
in the section that follows what you quoted.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help