From: Ralf Baechle <ralf@linux-mips.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Matthew Wilcox <matthew@wil.cx>, linux-arch@vger.kernel.org
Subject: Re: Removal of dma_cache_* functions?
Date: Tue, 4 Sep 2007 14:07:08 +0100 [thread overview]
Message-ID: <20070904130707.GA16556@linux-mips.org> (raw)
In-Reply-To: <1188910630.3435.2.camel@localhost.localdomain>
On Tue, Sep 04, 2007 at 01:57:10PM +0100, James Bottomley wrote:
> On Tue, 2007-09-04 at 06:42 -0600, Matthew Wilcox wrote:
> > On Tue, Sep 04, 2007 at 12:56:16PM +0100, Ralf Baechle wrote:
> > > Most architectures implement the dma_cache_wback, dma_cache_wback_inv
> > > and dma_cache_wback_inv functions even though there is the more modern
> > > and much better designed DMA API and only two MIPS-specific users (one of
> > > which I just fixed) do remain. So should we finally start removing it?
> >
> > There's still some users in arch/, but yes, let's remove it from the
> > arches that don't use it internally.
>
> There's the updated dma_cache_sync() API, which you need to keep because
> the parisc lasi scsi and network drivers rely on it for our fully
> incoherent boxes.
I wasn't thinking of touching dma_cache_sync, only the three mentioned
mostly unused ones.
Ralf
next prev parent reply other threads:[~2007-09-04 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 11:56 Removal of dma_cache_* functions? Ralf Baechle
2007-09-04 12:42 ` Matthew Wilcox
2007-09-04 12:57 ` James Bottomley
2007-09-04 13:07 ` Ralf Baechle [this message]
2007-09-04 23:49 ` James Bottomley
2007-09-11 13:44 ` Jes Sorensen
2007-09-11 13:58 ` Ralf Baechle
2007-09-04 13:07 ` Matthew Wilcox
2007-09-04 13:33 ` Ralf Baechle
2007-09-06 11:39 ` [PATCH] Removal of dma_cache_(wback|inv|wback_inv) functions Ralf Baechle
2007-09-06 14:55 ` Paul Mackerras
2007-09-06 15:02 ` David Miller
2007-09-06 15:02 ` Kyle McMartin
2007-09-06 21:28 ` Håvard Skinnemoen
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=20070904130707.GA16556@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=James.Bottomley@steeleye.com \
--cc=linux-arch@vger.kernel.org \
--cc=matthew@wil.cx \
/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).