From: James Bottomley <James.Bottomley@suse.de>
To: linux-arch@vger.kernel.org
Cc: linux-parisc@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Russell King <rmk@arm.linux.org.uk>,
Paul Mundt <lethal@linux-sh.org>,
James Bottomley <jejb@external.hp.com>
Subject: [PATCHv2 0/5] fix xfs by making I/O to vmap/vmalloc areas work
Date: Wed, 23 Dec 2009 15:22:20 -0600 [thread overview]
Message-ID: <1261603345-2494-1-git-send-email-James.Bottomley@suse.de> (raw)
From: James Bottomley <jejb@external.hp.com>
After looking through all the feedback, here's the next version of the
patch.
This one is based on a new api: flush/invalidate_kernel_vmap_range()
making it clear that the fs/driver is the entity managing the vmaps
... it also drops the block inputs because coherency management is now
the responsibility of the user. The xfs interface is nicely
simplified with this approach. Could someone check this on arm and
sh?
Thanks,
James
---
James Bottomley (5):
mm: add coherence API for DMA to vmalloc/vmap areas
parisc: add mm API for DMA to vmalloc/vmap areas
arm: add mm API for DMA to vmalloc/vmap areas
sh: add mm API for DMA to vmalloc/vmap areas
xfs: fix xfs to work with Virtually Indexed architectures
Documentation/cachetlb.txt | 27 +++++++++++++++++++++++++++
arch/arm/include/asm/cacheflush.h | 10 ++++++++++
arch/parisc/include/asm/cacheflush.h | 12 ++++++++++++
arch/sh/include/asm/cacheflush.h | 8 ++++++++
fs/xfs/linux-2.6/xfs_buf.c | 20 +++++++++++++++++++-
include/linux/highmem.h | 6 ++++++
6 files changed, 82 insertions(+), 1 deletions(-)
next reply other threads:[~2009-12-23 21:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 21:22 James Bottomley [this message]
2009-12-23 21:22 ` [PATCHv2 1/5] mm: add coherence API for DMA to vmalloc/vmap areas James Bottomley
2009-12-23 21:22 ` James Bottomley
2009-12-23 21:22 ` [PATCHv2 2/5] parisc: add mm " James Bottomley
2009-12-23 21:22 ` [PATCHv2 3/5] arm: " James Bottomley
2009-12-23 21:22 ` [PATCHv2 4/5] sh: " James Bottomley
2009-12-23 21:22 ` James Bottomley
2009-12-23 21:22 ` [PATCHv2 5/5] xfs: fix xfs to work with Virtually Indexed architectures James Bottomley
2009-12-24 11:03 ` Christoph Hellwig
2009-12-24 11:03 ` Christoph Hellwig
2009-12-27 15:32 ` James Bottomley
2010-01-02 21:33 ` [PATCHv2 2/5] parisc: add mm API for DMA to vmalloc/vmap areas Benjamin Herrenschmidt
2010-01-02 21:33 ` Benjamin Herrenschmidt
2010-01-02 21:53 ` James Bottomley
2010-01-03 20:12 ` Benjamin Herrenschmidt
2010-01-03 20:12 ` Benjamin Herrenschmidt
2009-12-24 10:08 ` [PATCHv2 1/5] mm: add coherence " Matt Fleming
2009-12-24 10:08 ` Matt Fleming
2009-12-24 12:39 ` Matthew Wilcox
2009-12-24 12:39 ` Matthew Wilcox
2009-12-24 13:06 ` Matt Fleming
2009-12-24 13:06 ` Matt Fleming
2009-12-27 15:37 ` James Bottomley
2010-01-02 21:27 ` Benjamin Herrenschmidt
2010-01-02 21:54 ` James Bottomley
2010-01-03 20:14 ` Benjamin Herrenschmidt
2010-01-03 20:14 ` Benjamin Herrenschmidt
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=1261603345-2494-1-git-send-email-James.Bottomley@suse.de \
--to=james.bottomley@suse.de \
--cc=hch@lst.de \
--cc=jejb@external.hp.com \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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).