From: Octavian Purdila <opurdila@ixiacom.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] ramfs: enable splice write
Date: Sat, 21 Jun 2008 15:36:18 +0300 [thread overview]
Message-ID: <200806211536.18484.opurdila@ixiacom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 182 bytes --]
Hi Andrew,
Any reason for which we don't enable splice write in ramfs? The following
patch seems to make splice write work on my system (only tested the MMU
path).
Thanks,
tavi
[-- Attachment #2: Type: text/plain, Size: 1050 bytes --]
commit da8e2b1f4d096796a5e2f1b11d4a32a78eca0eae
Author: Octavian Purdila <opurdila@ixiacom.com>
Date: Sat Jun 21 15:14:40 2008 +0300
ramfs: enable splice write
Signed-off-by: Octavian Purdila <opurdila@ixiacom.com>
diff --git a/fs/ramfs/file-mmu.c b/fs/ramfs/file-mmu.c
index 9590b90..78f613c 100644
--- a/fs/ramfs/file-mmu.c
+++ b/fs/ramfs/file-mmu.c
@@ -45,6 +45,7 @@ const struct file_operations ramfs_file_operations = {
.mmap = generic_file_mmap,
.fsync = simple_sync_file,
.splice_read = generic_file_splice_read,
+ .splice_write = generic_file_splice_write,
.llseek = generic_file_llseek,
};
diff --git a/fs/ramfs/file-nommu.c b/fs/ramfs/file-nommu.c
index 0989bc2..52312ec 100644
--- a/fs/ramfs/file-nommu.c
+++ b/fs/ramfs/file-nommu.c
@@ -43,6 +43,7 @@ const struct file_operations ramfs_file_operations = {
.aio_write = generic_file_aio_write,
.fsync = simple_sync_file,
.splice_read = generic_file_splice_read,
+ .splice_write = generic_file_splice_write,
.llseek = generic_file_llseek,
};
reply other threads:[~2008-06-21 12:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200806211536.18484.opurdila@ixiacom.com \
--to=opurdila@ixiacom.com \
--cc=akpm@linux-foundation.org \
--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®