Re: [RFC] Heads up on sys_fallocate()
From: Jan Engelhardt <hidden>
Date: 2007-03-02 13:41:01
Also in:
linux-fsdevel, lkml
From: Jan Engelhardt <hidden>
Date: 2007-03-02 13:41:01
Also in:
linux-fsdevel, lkml
On Mar 1 2007 23:09, Dave Kleikamp wrote:
quoted
Given that glibc already implements fallocate for all filesystems, it will need to continue to do so for filesystems which don't implement this syscall - otherwise applications would start breaking.I didn't make it clear, but my point was to call generic_fallocate if the file system did not define i_op->allocate(). if (inode->i_op && inode->i_op->fallocate) ret = inode->i_op->fallocate(inode, offset, len); else ret = generic_fallocate(inode, offset, len); I'm not sure it's worth the effort, but I thought I'd throw the idea out there.
Writing zeroes using glibc emu most likely means write() -- so generic_fallocate should be preferable (think splice). Or does glibc use mmap() and it's all different? Jan --