From: Tom Rini <trini@kernel.crashing.org>
To: linuxppc-embedded@lists.linuxppc.org,
Paul Mackerras <paulus@samba.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: consistent_free()
Date: Tue, 25 Jun 2002 07:39:37 -0700 [thread overview]
Message-ID: <20020625143937.GN3489@opus.bloom.county> (raw)
In-Reply-To: <20020624021538.GX9087@zax>
On Mon, Jun 24, 2002 at 12:15:38PM +1000, David Gibson wrote:
>
> On Fri, Jun 14, 2002 at 03:57:11PM +1000, David Gibson wrote:
> >
> > On Fri, Jun 14, 2002 at 02:29:28PM +1000, David Gibson wrote:
> > >
> > > In attempting to make consistent_alloc/free() work sensibly on
> > > processors which are cache coherent I ran into a problem.
> > > consistent_free() doesn't take a size argument. We don't need it in
> > > the case of not cache coherent processors - in that case
> > > consistent_alloc() sets up a vm_area() so there's enough information
> > > to get the size. However for cache coherent processors we probably
> > > want consistent_alloc() to degenerate to __get_free_pages(), in which
> > > case consistent_free() must degenerate to free_pages(), which takes a
> > > size argument.
> > >
> > > I suggest we change consistent_free() to take the virtual addresss,
> > > size and the physical address (dma_addr_t), which will make our
> > > consistent_free() match the one on ARM. I know we don't need the
> > > third argument in any existing situation.
> > >
> > > Patch coming...
> >
> > As promised...
> >
> > This boots up fine on my EP405PC board, and I'm sending this mail from
> > my TiBook running 2_4_devel with this patch and also the 40x large
> > page PMD patch.
>
> Again, silence reigns. Anyone who would object to this being applied
> to the linuxppc-2.5 tree, speak up now.
If we're going to touch this, can you look at the current ARM version of
it and grab all of the goodies they've got now? I almost had this going
(and I can shoot you the patch off the list if you like) but haven't had
time to go back to it.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-25 14:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 4:29 consistent_free() David Gibson
2002-06-14 5:57 ` consistent_free() David Gibson
2002-06-24 2:15 ` consistent_free() David Gibson
2002-06-25 14:39 ` Tom Rini [this message]
2002-06-26 5:17 ` consistent_free() David Gibson
2002-06-26 5:33 ` consistent_free() Dan Malek
2002-06-26 5:59 ` consistent_free() David Gibson
2002-06-26 14:32 ` consistent_free() Paul Mackerras
2002-06-27 2:42 ` consistent_free() David Gibson
2002-06-14 15:39 ` consistent_free() Tom Rini
2002-06-14 16:44 ` consistent_free() Dan Malek
2002-06-14 17:10 ` consistent_free() Tom Rini
2002-06-14 21:34 ` consistent_free() Dan Malek
2002-06-15 6:11 ` consistent_free() Paul Mackerras
2002-06-15 6:42 ` consistent_free() Dan Malek
2002-06-15 10:02 ` consistent_free() Paul Mackerras
2002-06-15 13:51 ` consistent_free() Dan Malek
2002-06-15 6:02 ` consistent_free() Paul Mackerras
2002-06-15 6:27 ` consistent_free() Dan Malek
2002-06-15 6:57 ` consistent_free() David Gibson
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=20020625143937.GN3489@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).