linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Paul Mackerras <paulus@samba.org>
Cc: David Gibson <david@gibson.dropbear.id.au>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: First cut at large page support on 40x
Date: Thu, 06 Jun 2002 00:48:35 -0400	[thread overview]
Message-ID: <3CFEE9A3.5060300@embeddededge.com> (raw)
In-Reply-To: 15614.37065.549142.218906@argo.ozlabs.ibm.com


Paul Mackerras wrote:

> Dan, you continue to surprise me.

Eh?

> .....  You complain about a kB or two for
> a device tree

When did I ever complain about a device tree?  I think it's the right
idea, I just didn't like the way we were getting there on systems
that don't have OF.

> .... but happily throw away anything from 16kB to 128kB or
> more just to simplify iopa, which should not be needed anyway.

What isn't needed?  The page tables or the iopa()?  I'm tired of having
different methods to look up VM information just because the memory
was allocated in a different way.  With iopa() (which seems fine for
other architectures to use) I don't care how the memory was allocated,
I just feed it a virtual address and get the answer.  What's wrong with
that (other than it's not a hack :-)?  The page tables have always
been there, and it's not a big deal.  Why haven't we done the same
hack for processors with BATs?  They don't need the page tables either.

I also stated the importance of the page tables is to allow background
hardware debuggers to look up translations so they can work with Linux.
Kind of a nice thing to have once in a while.

I find a simple solution for an enhancement and you don't like it because
it isn't a big hacked up mess (or maybe because I had an original thought).
If I would have made the same hacked up mess you have done it wouldn't have
been checked in.....not long ago all of the embedded stuff was viewed as a
problem child, and today it's OK to hack up generic code with an #ifdef
for a specific IBM embedded processor????  Does that surprise you? :-)

I haven't changed my point of view on any of the embedded Linux because
that is pretty much all I have ever done.  It's the rest of you that can't
determine on which side of the fence you want to play.  Stop picking on me
or I'll take all of my toys to a different playground :-).


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-06  4:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-31  4:21 First cut at large page support on 40x David Gibson
2002-05-31  4:31 ` David Gibson
2002-06-04  0:43 ` Dan Malek
2002-06-04  3:59   ` David Gibson
2002-06-04 17:42     ` Dan Malek
2002-06-05  0:10       ` David Gibson
2002-06-05 17:25         ` Dan Malek
2002-06-06  1:35           ` David Gibson
2002-06-06  4:57             ` Dan Malek
2002-06-05 22:29       ` Paul Mackerras
2002-06-06  4:48         ` Dan Malek [this message]
2002-06-06  5:44           ` Paul Mackerras
2002-06-06  7:58             ` Dan Malek
2002-06-06  8:17               ` David Gibson
2002-06-12  3:52               ` David Gibson
2002-06-12  6:15                 ` Dan Malek
2002-06-12  6:43                   ` David Gibson
2002-06-12 15:19                     ` Tom Rini
2002-06-12 23:23                     ` Dan Malek
2002-06-12 23:42                       ` Paul Mackerras
2002-06-13  0:28                         ` Dan Malek
2002-06-13  1:01                           ` Paul Mackerras
2002-06-13  4:16                             ` Dan Malek
2002-06-13  5:12                               ` David Gibson
2002-06-13  7:26                                 ` Dan Malek
2002-06-13  1:38                       ` Paul Mackerras
2002-06-13  4:47                         ` Dan Malek
2002-06-13 18:13                     ` Armin
2002-06-14  0:33                       ` David Gibson
2002-06-12 23:49                   ` Paul Mackerras

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=3CFEE9A3.5060300@embeddededge.com \
    --to=dan@embeddededge.com \
    --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).