On Mon, Apr 30, 2007 at 03:56:32PM +1000, David Chinner wrote:
> On Sun, Apr 29, 2007 at 10:25:59PM -0700, Chris Wedgwood wrote:
> IIRC, the argument for FA_ALLOCATE changing file size is that
> posix_fallocate() is supposed to change the file size.
But it's not posix_fallocate; it's something mo
On Sun, Apr 29, 2007 at 10:25:59PM -0700, Chris Wedgwood wrote:
> On Mon, Apr 30, 2007 at 10:47:02AM +1000, David Chinner wrote:
>
> > For FA_ALLOCATE, it's supposed to change the file size if we
> > allocate past EOF, right?
>
> I would argue no. Use truncate for that.
I'm going from the ext4
On Mon, Apr 30, 2007 at 10:47:02AM +1000, David Chinner wrote:
> For FA_ALLOCATE, it's supposed to change the file size if we
> allocate past EOF, right?
I would argue no. Use truncate for that.
> For FA_DEALLOCATE, does it change the filesize at all?
Same as above.
> Or does
> it just punch
Add new mode to ->fallocate() to allow allocation to occur
beyond the current EOF without changing the file size. Implement
in XFS ->fallocate() vector.
Signed-Off-By: Dave Chinner <[EMAIL PROTECTED]>
---
fs/xfs/linux-2.6/xfs_iops.c |8 +---
include/linux/fs.h |1 +
2 files
Add XFS support for ->fallocate() vector.
Signed-Off-By: Dave Chinner <[EMAIL PROTECTED]>
---
fs/xfs/linux-2.6/xfs_iops.c | 48
1 file changed, 48 insertions(+)
Index: 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_iops.c
==
ia64 fallocate syscall support.
Signed-Off-By: Dave Chinner <[EMAIL PROTECTED]>
---
arch/ia64/kernel/entry.S |1 +
include/asm-ia64/unistd.h |3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
Index: 2.6.x-xfs-new/arch/ia64/kernel/entry.S
===
On Thu, Apr 26, 2007 at 11:20:56PM +0530, Amit K. Arora wrote:
> Based on the discussion, this new patchset uses following as the
> interface for fallocate() system call:
>
> asmlinkage long sys_fallocate(int fd, int mode, loff_t offset, loff_t len)
Ok, so now for the hard questions - what are t
Lee Revell wrote:
On 4/28/07, Mikulas Patocka <[EMAIL PROTECTED]> wrote:
I most wonder, why vim fsyncs its swapfile regularly (blocking typing
during that) and doesn't fsync the resulting file on :w :-/
Never seen this. Why would fsync block typing unless vim was doing
disk IO for every keys
