mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Cavanagh <steven.cavanagh@secretlab.ca>
To: hirofumi@mail.parknet.co.jp
Cc: linux-kernel@vger.kernel.org, grant.likely@secretlab.ca
Subject: [PATCH] fat: Editions to support fat_fallocate()
Date: Sat, 22 Dec 2007 14:09:58 -0700	[thread overview]
Message-ID: <20071222210958.9351.35913.stgit@jpe-laptop> (raw)

From: Steven Cavanagh <steven.cavanagh@secretlab.ca>

Added support for fallocate for a msdos fat driver. This allows
preallocation of clusters to an inode before writes to reduce
file fragmentation

Signed-off-by: Steven.Cavanagh <steven.cavanagh@secretlab.ca>
---

 fs/fat/file.c |   45 +++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 45 insertions(+), 0 deletions(-)

diff --git a/fs/fat/file.c b/fs/fat/file.c
index 69a83b5..f753c6a 100644
--- a/fs/fat/file.c
+++ b/fs/fat/file.c
@@ -15,6 +15,7 @@ #include <linux/buffer_head.h>
 #include <linux/writeback.h>
 #include <linux/backing-dev.h>
 #include <linux/blkdev.h>
+#include <linux/falloc.h>
 
 int fat_generic_ioctl(struct inode *inode, struct file *filp,
 		      unsigned int cmd, unsigned long arg)
@@ -312,8 +313,52 @@ int fat_getattr(struct vfsmount *mnt, st
 }
 EXPORT_SYMBOL_GPL(fat_getattr);
 
+/*
+ * preallocate space for a file. This implements fat fallocate inode
+ * operation, which gets called from sys_fallocate system call. User
+ * space requests len bytes at offset.
+ */
+long fat_fallocate(struct inode *inode, int mode, loff_t offset, loff_t len)
+{
+	int ret = 0;
+	loff_t filesize = inode->i_size;
+
+	/* preallocation to directories is currently not supported */
+	if (S_ISDIR(inode->i_mode)) {
+		printk(KERN_ERR
+		"fat_fallocate(): Directory prealloc not supported\n");
+		return -ENODEV;
+	}
+
+	if ((offset + len) <= MSDOS_I(inode)->mmu_private) {
+		printk(KERN_INFO
+			"fat_fallocate():Blocks already allocated\n");
+			return 0;
+	}
+
+	if ((offset + len) > MSDOS_I(inode)->mmu_private) {
+
+		mutex_lock(&inode->i_mutex);
+		ret = fat_cont_expand(inode, (offset + len));
+		if (ret) {
+			printk(KERN_ERR
+				"fat_fallocate():fat_cont_expand() error\n");
+			mutex_unlock(&inode->i_mutex);
+			return ret;
+		}
+		mutex_unlock(&inode->i_mutex);
+	}
+	if (mode & FALLOC_FL_KEEP_SIZE) {
+		mutex_lock(&inode->i_mutex);
+		i_size_write(inode, filesize);
+		mutex_unlock(&inode->i_mutex);
+	}
+	return ret;
+}
+
 const struct inode_operations fat_file_inode_operations = {
 	.truncate	= fat_truncate,
 	.setattr	= fat_notify_change,
 	.getattr	= fat_getattr,
+	.fallocate	= fat_fallocate,
 };

             reply	other threads:[~2007-12-22 22:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-22 21:09 Steven Cavanagh [this message]
2007-12-22 22:18 ` Grant Likely
2007-12-23 12:16   ` OGAWA Hirofumi
2007-12-23 20:23     ` Grant Likely
2008-01-13 19:49       ` OGAWA Hirofumi
     [not found] <20071214193017.7545.88989.stgit@jpe-laptop>
2007-12-14 20:12 ` Grant Likely
  -- strict thread matches above, loose matches on Subject: below --
2007-12-12  0:20 Steven Cavanagh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071222210958.9351.35913.stgit@jpe-laptop \
    --to=steven.cavanagh@secretlab.ca \
    --cc=grant.likely@secretlab.ca \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®