linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Kanoj Sarcar <kanoj@google.engr.sgi.com>
Cc: "David S. Miller" <davem@redhat.com>,
	alan@lxorguk.ukuu.org.uk, sct@redhat.com, roman@augan.com,
	linux-mm@kvack.org, linux-kernel@vger.rutgers.edu,
	rmk@arm.linux.org.uk, nico@cam.org, davidm@hpl.hp.com
Subject: Re: pte_pagenr/MAP_NR deleted in pre6
Date: Thu, 7 Sep 2000 16:31:44 +0200	[thread overview]
Message-ID: <20000907163144.E6580@bacchus.dhis.org> (raw)
In-Reply-To: <200008171936.MAA31128@google.engr.sgi.com>; from kanoj@google.engr.sgi.com on Thu, Aug 17, 2000 at 12:36:51PM -0700

On Thu, Aug 17, 2000 at 12:36:51PM -0700, Kanoj Sarcar wrote:

> >    Except for the x86 36bit abortion do we need a long long paddr_t on any
> >    32bit platform ?
> > 
> > Sparc32, mips32...
> >
> 
> Not for Indys on mips32. Is there a mips32 port on another machine
> (currently in Linux, or port ongoing) that requires this?

No.  Right now mips32 assumes that all memory is accessible in KSEG0 which
limits it to 512mb - $\epsilon$.  I don't know of any 32-bit CPU
configuration which supports memory than that and for 64-bit processors
the policy should be to use mips64 - it's so much saner.

  Ralf
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-09-07 14:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-10 17:18 Kanoj Sarcar
2000-08-11  2:24 ` David S. Miller
2000-08-14  0:34   ` Anton Blanchard
2000-08-11 11:50 ` Roman Zippel
2000-08-11 13:20   ` Russell King
2000-08-11 14:56     ` Roman Zippel
2000-08-12  9:18       ` Bjorn Wesen
2000-08-11 17:21     ` Kanoj Sarcar
2000-08-14  9:29       ` Roman Zippel
2000-08-15 16:19 ` Stephen C. Tweedie
2000-08-16  8:25   ` Roman Zippel
2000-08-16 17:13     ` Kanoj Sarcar
2000-08-16 18:20       ` Stephen C. Tweedie
2000-08-16 18:24         ` David S. Miller
2000-08-16 19:53           ` Stephen C. Tweedie
2000-08-16 18:47         ` Kanoj Sarcar
2000-08-16 18:39           ` David S. Miller
2000-08-16 19:30             ` Stephen C. Tweedie
2000-08-16 22:22         ` Kanoj Sarcar
2000-08-17  9:11           ` Stephen C. Tweedie
2000-08-17 19:07             ` Kanoj Sarcar
2000-08-17 19:01               ` David S. Miller
2000-08-17 19:19                 ` Alan Cox
2000-08-17 19:20                   ` David S. Miller
2000-08-17 19:33                     ` Alan Cox
2000-08-17 19:36                     ` Kanoj Sarcar
2000-09-07 14:31                       ` Ralf Baechle [this message]
2000-08-17 19:50                     ` Kanoj Sarcar
2000-08-17 19:41                       ` David S. Miller
2000-09-07 14:26                         ` Ralf Baechle
2000-08-17 19:56                       ` Alan Cox
2000-08-17 19:24                   ` Alan Cox
2000-08-17 19:32                 ` Kanoj Sarcar
2000-08-17 19:30                   ` David S. Miller
2000-08-17 20:00                     ` Kanoj Sarcar
2000-08-16 18:17     ` Stephen C. Tweedie

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=20000907163144.E6580@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=kanoj@google.engr.sgi.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=nico@cam.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=roman@augan.com \
    --cc=sct@redhat.com \
    /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