xfs
[Top] [All Lists]

Re: [PATCH] Implement fallocate

To: David Chinner <dgc@xxxxxxx>
Subject: Re: [PATCH] Implement fallocate
From: Lachlan McIlroy <lachlan@xxxxxxx>
Date: Thu, 01 Nov 2007 12:15:45 +1100
Cc: xfs@xxxxxxxxxxx, xfs-dev@xxxxxxx
In-reply-to: <20071029233841.GT995458@xxxxxxx>
References: <20071029233841.GT995458@xxxxxxx>
Reply-to: lachlan@xxxxxxx
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.6 (X11/20070728)
David Chinner wrote:
XFS fallocate() callout.

Allocate the range requested as unwritten extents. Atomically
change the file size if requested.

Signed-off-by: Dave Chinner <dgc@xxxxxxx>
---
 fs/xfs/linux-2.6/xfs_iops.c |   45 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 45 insertions(+)

Index: 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_iops.c
===================================================================
--- 2.6.x-xfs-new.orig/fs/xfs/linux-2.6/xfs_iops.c      2007-10-30 
10:18:59.061735503 +1100
+++ 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_iops.c   2007-10-30 10:19:26.498185998 
+1100
@@ -52,6 +52,7 @@
 #include <linux/xattr.h>
 #include <linux/namei.h>
 #include <linux/security.h>
+#include <linux/falloc.h>
/*
  * Bring the atime in the XFS inode uptodate.
@@ -796,6 +797,49 @@ xfs_vn_removexattr(
        return namesp->attr_remove(vp, attr, xflags);
 }
+/*
+ * generic space allocation vector.
+ */
+STATIC long
+xfs_vn_fallocate(
+       struct inode    *inode,
+       int             mode,
+       loff_t          offset,
+       loff_t          len)
+{
+       long            error;
+       loff_t          new_size = 0;
+       xfs_flock64_t   bf;
+
+       /* preallocation on directories not yet supported */
+       error = -ENODEV;
+       if (S_ISDIR(inode->i_mode))
+               goto out_error;
+
+       bf.l_whence = 0;
+       bf.l_start = offset;
+       bf.l_len = len;
+
+       xfs_ilock(XFS_I(inode), XFS_IOLOCK_EXCL);
+       error = xfs_change_file_space(XFS_I(inode), XFS_IOC_RESVSP, &bf,
+                                               0, NULL, ATTR_NOLOCK);
+       if (!error && !(mode & FALLOC_FL_KEEP_SIZE) &&
+           offset + len > i_size_read(inode))
+               new_size = offset + len;
+
+       /* Change file size if needed */
+       if (new_size) {
+               bhv_vattr_t     va;
+
+               va.va_mask = XFS_AT_SIZE;
+               va.va_size = new_size;
+               error = xfs_setattr(XFS_I(inode), &va, ATTR_NOLOCK, NULL);
+       }

Is it necessary to call xfs_setattr() here?  Could we just do an explicit
call to xfs_zero_eof(), set the new size, set i_update_core/size and mark
the inode dirty?  Hmmm, then again, that approach wouldn't be as clean as
above.

+
+       xfs_iunlock(XFS_I(inode), XFS_IOLOCK_EXCL);
+out_error:
+       return error;
+}
const struct inode_operations xfs_inode_operations = {
        .permission             = xfs_vn_permission,
@@ -806,6 +850,7 @@ const struct inode_operations xfs_inode_
        .getxattr               = xfs_vn_getxattr,
        .listxattr              = xfs_vn_listxattr,
        .removexattr            = xfs_vn_removexattr,
+       .fallocate              = xfs_vn_fallocate,
 };
const struct inode_operations xfs_dir_inode_operations = {



<Prev in Thread] Current Thread [Next in Thread>