From: "Ken Chen" <kenchen@google.com>
To: Hugh Dickins <hugh@veritas.com>, Andrew Morton <akpm@osdl.org>
Cc: linux-mm@kvack.org
Subject: [patch] convert ramfs to use __set_page_dirty_no_writeback
Date: Wed, 31 Jan 2007 14:39:19 -0800 [thread overview]
Message-ID: <b040c32a0701311439y2e0ba4e6qcc25bc4d4ab8f7e4@mail.gmail.com> (raw)
As pointed out by Hugh, ramfs would also benefit from using the new
set_page_dirty aop method for memory backed file systems.
Signed-off-by: Ken Chen <kenchen@google.com>
---
Hugh, I chickened out on swap_aops() as I'd rather not to muck with code
that I'm not familiar with.
--- ./fs/ramfs/file-mmu.c.orig 2007-01-31 13:27:14.000000000 -0800
+++ ./fs/ramfs/file-mmu.c 2007-01-31 13:27:39.000000000 -0800
@@ -31,7 +31,7 @@
.readpage = simple_readpage,
.prepare_write = simple_prepare_write,
.commit_write = simple_commit_write,
- .set_page_dirty = __set_page_dirty_nobuffers,
+ .set_page_dirty = __set_page_dirty_no_writeback,
};
const struct file_operations ramfs_file_operations = {
--- ./fs/ramfs/file-nommu.c.orig 2007-01-31 13:27:27.000000000 -0800
+++ ./fs/ramfs/file-nommu.c 2007-01-31 13:28:21.000000000 -0800
@@ -32,7 +32,7 @@
.readpage = simple_readpage,
.prepare_write = simple_prepare_write,
.commit_write = simple_commit_write,
- .set_page_dirty = __set_page_dirty_nobuffers,
+ .set_page_dirty = __set_page_dirty_no_writeback,
};
const struct file_operations ramfs_file_operations = {
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2007-01-31 22:39 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=b040c32a0701311439y2e0ba4e6qcc25bc4d4ab8f7e4@mail.gmail.com \
--to=kenchen@google.com \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).