From: David Cross <david.cross@cypress.com>
To: dhowells@redhat.com
Cc: linux-cachefs@redhat.com, greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Cachefiles, mpage_cleardirty addtition, west bridge related
Date: Tue, 07 Sep 2010 12:33:31 -0700 [thread overview]
Message-ID: <1283888011.7250.17.camel@odc-laptop> (raw)
This patch adds the mpage_cleardirty function to the cachefiles implementation in the kernel.
The purpose behind this patch is to allow for file based DMA through an external DMA engine
without the data ever going through the process. The procedure for the usage of this function
is as follows:
1) User space allocates and maps a file
2) external DMA device transfers the data to non-volatile storage directly without it going through
the processor
3) the "dirty" pages must be cleared and invalidated as they do not contain correct information.
I believe that David is the correct maintainer and am hoping that he is willing to ACK this change. Please let me know
if there are any issues or concerns with this patch or if I should be
asking a different maintainer to ack.
Thanks,
David
Signed-off-by: David Cross <david.cross@cypress.com>
diff -uprN -X linux-next-vanilla/Documentation/dontdiff linux-next-vanilla/fs/mpage.c linux-next-incl-sdk/fs/mpage.c
--- linux-next-vanilla/fs/mpage.c 2010-08-31 19:32:51.000000000 -0700
+++ linux-next-incl-sdk/fs/mpage.c 2010-09-07 11:52:39.000000000 -0700
@@ -716,3 +716,50 @@ int mpage_writepage(struct page *page, g
return ret;
}
EXPORT_SYMBOL(mpage_writepage);
+
+int mpage_cleardirty(struct address_space *mapping, int num_pages)
+{
+ int ret = 0;
+ int nr_pages;
+ struct pagevec pvec;
+ pgoff_t index = 0;
+ pgoff_t end;
+
+ pagevec_init(&pvec, 0);
+ index = mapping->writeback_index;
+ end = index + num_pages;
+
+ while ((index <= end) &&
+ (nr_pages = pagevec_lookup_tag(&pvec, mapping, &index,
+ PAGECACHE_TAG_DIRTY, min(end - index,
+ (pgoff_t)PAGEVEC_SIZE-1) + 1))) {
+ unsigned i;
+
+ for (i = 0; i < nr_pages; i++) {
+ struct page *page = pvec.pages[i];
+
+ lock_page(page);
+ ret = clear_page_dirty_for_io(page);
+ if (page_has_private(page))
+ do_invalidatepage(page, 0);
+
+ cancel_dirty_page(page, PAGE_CACHE_SIZE);
+
+ remove_from_page_cache(page);
+ ClearPageMappedToDisk(page);
+ page_cache_release(page); /* pagecache ref */
+ unlock_page(page);
+
+ if (!ret) {
+ printk(KERN_INFO "mpage_cleardirty: "
+ "clear_page_dirty_for_io returned %d\n", ret);
+ return ret;
+ }
+ }
+ pagevec_release(&pvec);
+ cond_resched();
+ }
+
+ return ret;
+}
+EXPORT_SYMBOL(mpage_cleardirty);
---------------------------------------------------------------
This message and any attachments may contain Cypress (or its
subsidiaries) confidential information. If it has been received
in error, please advise the sender and immediately delete this
message.
---------------------------------------------------------------
next reply other threads:[~2010-09-07 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 19:33 David Cross [this message]
2010-09-07 23:59 ` Greg KH
2010-09-08 17:02 ` [PATCH] Cachefiles, mpage_cleardirty addtition, west bridgerelated David Cross
2010-09-08 14:35 ` [PATCH] Cachefiles, mpage_cleardirty addtition, west bridge related David Howells
2010-09-08 16:51 ` David Cross
2010-09-08 21:05 ` Christoph Hellwig
2010-09-08 21:20 ` David Cross
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=1283888011.7250.17.camel@odc-laptop \
--to=david.cross@cypress.com \
--cc=dhowells@redhat.com \
--cc=greg@kroah.com \
--cc=linux-cachefs@redhat.com \
--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®