archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <>
To: (Matt Nelson)
Subject: Re: Any limitations on bigmem usage?
Date: Tue, 12 Jun 2001 17:29:14 +0100 (BST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> from "Matt Nelson" at Jun 11, 2001 05:18:09 PM

> Specifically, is there anything to prevent me from malloc()ing 6GB of memory, 
> then accessing that memory as I would any other buffer?  FYI, the application

X86 has no nice way to address over 4Gb of RAM. You can do paging games with
multiple banks and shmat (ie like using DOS expanded ram but with bigger

> I've been eyeing an 8-way Intel box with gobs of memory, but if there are subtle 
> issues with using that much memory, I need to know now.

If your algorithm can work well with say 2Gb windows on the data and only change
window evey so often (in computing terms) then it should be ok, if its access
is random you need to look at a 64bit box like an Alpha, Sparc64 or eventually

  parent reply	other threads:[~2001-06-12 16:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12  0:18 Matt Nelson
2001-06-12  0:31 ` Doug McNaught
2001-06-12  0:38   ` Doug McNaught
2001-06-12 14:03 ` Matt Nelson
2001-06-12 16:29 ` Alan Cox [this message]
2001-06-12 12:46   ` Rob Landley
2001-06-12 18:16     ` Rik van Riel
2001-06-12 18:34 Holzrichter, Bruce
2001-06-13 10:39 ` Ralf Baechle

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: Any limitations on bigmem usage?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).