Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Matthew Dharm <mdharm@momenco.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: MIPS64 status?
Date: Mon, 14 Jan 2002 15:45:42 -0800	[thread overview]
Message-ID: <20020114154542.A29462@dea.linux-mips.net> (raw)
In-Reply-To: <NEBBLJGMNKKEEMNLHGAICENCCEAA.mdharm@momenco.com>; from mdharm@momenco.com on Mon, Jan 14, 2002 at 03:25:44PM -0800

On Mon, Jan 14, 2002 at 03:25:44PM -0800, Matthew Dharm wrote:

> Thanks for the info.  Too bad "MIPS64" and "mips64" sound exactly the
> same on the telephone.
> 
> But, I need to be pedantic, just to be clear on a couple of
> questions...
> 
> So, the "mips64" kernel can use 64-bits of address, for RAM >4G?
> But, the apps running are always 32-bit?

In theory the kernel has the capability to run 64-bit applications.  In
practice that doesn't work due to the lack of 64-bit apps and stuff.

> Does this mean that any individual application can only use 4G of
> memory, tho you could have several applications in physical memory
> doing this? (i.e. multiple applications using 1G of RAM each, but not
> swapping to disk?)

In theory we don't limit the address space of 32-bit applications in 64-bit
mode so they could go and use all memory and syscalls on the 64-bit
address space also.  In practice that's just too ugly to be usable so
consider 32-bit apps on the 64-bit kernel as limited to 2gb as they are
currently.  You can however run an arbitrary number of these processes.

> Does this mean we could map PCI memory/IO addresses above 4G and have
> it work?

Sure.

  Ralf

  parent reply	other threads:[~2002-01-15  0:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14  5:13 MIPS64 status? Matthew Dharm
2002-01-14  8:13 ` Jason Gunthorpe
2002-01-14 20:00   ` Matthew Dharm
2002-01-14 20:00     ` Matthew Dharm
2002-01-14 20:42     ` Jason Gunthorpe
2002-01-14 23:07       ` Ralf Baechle
2002-01-15  0:08         ` Jason Gunthorpe
2002-01-15 20:59           ` Ralf Baechle
2002-01-15 20:00         ` John Heil
2002-01-15 20:55           ` Ralf Baechle
2002-01-16 18:55           ` Dominic Sweetman
2002-01-14 21:17     ` Dominic Sweetman
2002-01-14 21:17       ` Dominic Sweetman
2002-01-14 23:09       ` Ralf Baechle
2002-01-14 11:17 ` Dominic Sweetman
2002-01-14 12:54   ` Kevin D. Kissell
2002-01-14 12:54     ` Kevin D. Kissell
2002-01-14 13:37     ` Maciej W. Rozycki
2002-01-14 23:23     ` Ralf Baechle
2002-01-15 13:07       ` Maciej W. Rozycki
2002-01-14 23:22   ` Ralf Baechle
2002-01-15 19:11   ` Thiemo Seufer
2002-01-14 23:05 ` Ralf Baechle
2002-01-14 23:25   ` Matthew Dharm
2002-01-14 23:25     ` Matthew Dharm
2002-01-14 23:45     ` Ralf Baechle [this message]
2002-01-14 23:59     ` Jason Gunthorpe
2002-01-15  0:27       ` Matthew Dharm
2002-01-15  0:27         ` Matthew Dharm

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=20020114154542.A29462@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=mdharm@momenco.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