From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Matthew Wilcox <matthew@wil.cx>,
Matt Fleming <matt@console-pimps.org>,
linux-arch@vger.kernel.org, linux-parisc@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
Russell King <rmk@arm.linux.org.uk>,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCHv2 1/5] mm: add coherence API for DMA to vmalloc/vmap areas
Date: Mon, 04 Jan 2010 07:14:21 +1100 [thread overview]
Message-ID: <1262549661.2173.262.camel@pasglop> (raw)
In-Reply-To: <1262469295.2741.30.camel@mulgrave.site>
On Sat, 2010-01-02 at 15:54 -0600, James Bottomley wrote:
> Well, that's the result of the email thread. XFS is poking deeply into
> architectural issues by trying to do I/O on a vmap area. I thought the
> consensus was that if xfs wants to do that then it takes complete
> responsibility for coherence rather than trying to hide it in a block
> API.
Well, maybe ... Mostly my comment was about the "other" (standard) DMA
APIs, ie, the work you do for XFS just reminded me of that issue I've
been thinking about :-)
Cheers,
Ben.
prev parent reply other threads:[~2010-01-03 20:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 21:22 [PATCHv2 0/5] fix xfs by making I/O to vmap/vmalloc areas work James Bottomley
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 ` [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 ` [PATCHv2 5/5] xfs: fix xfs to work with Virtually Indexed architectures James Bottomley
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:53 ` James Bottomley
2010-01-03 20:12 ` Benjamin Herrenschmidt
2009-12-24 10:08 ` [PATCHv2 1/5] mm: add coherence " Matt Fleming
2009-12-24 12:39 ` Matthew Wilcox
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 [this message]
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=1262549661.2173.262.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=James.Bottomley@suse.de \
--cc=hch@lst.de \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=matthew@wil.cx \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.