From: Christoph Hellwig <hch@infradead.org>
To: David Cross <david.cross@cypress.com>
Cc: dhowells@redhat.com, linux-cachefs@redhat.com, greg@kroah.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Cachefiles, mpage_cleardirty addtition, west bridge related
Date: Wed, 8 Sep 2010 17:05:53 -0400 [thread overview]
Message-ID: <20100908210553.GA22411@infradead.org> (raw)
In-Reply-To: <9465F8A421744836B35704023ECA8253@stanford.edu>
On Wed, Sep 08, 2010 at 09:51:22AM -0700, David Cross wrote:
> This is used by the current west bridge driver in the linux-next tree,
> marked as BROKEN at the moment. It is used in order to clear dirty pages
> from the page cache for a specific file after it has been allocated. This
> allows west bridge to transfer data from USB to storage directly without
> requiring that the file data path go through the CPU. The easiest way to
> think of this is that it allows for direct file based DMA. Please let me
> know if you have any additional questions or concerns on this.
It's sad enough that it was taken into any tree at all, but we're not
going to add incorrect crap into the kernel kernel for it.
mpage_* are pagecache manpipulation routines, and are only for use by
filesystems for inodes they manage. A driver may never access this
directly. Is this the same piece of junk you wanted fat_get_block
exported for?
next prev parent reply other threads:[~2010-09-08 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 19:33 [PATCH] Cachefiles, mpage_cleardirty addtition, west bridge related David Cross
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 [this message]
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=20100908210553.GA22411@infradead.org \
--to=hch@infradead.org \
--cc=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