archive mirror
 help / color / mirror / Atom feed
From: Matt Nelson <>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Subject: Re: Any limitations on bigmem usage?
Date: Tue, 12 Jun 2001 07:03:40 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Thanks to all that replied.  I've never needed to use so much memory before, and 
was ignorant to how much magic was implemented in the 64G support on IA32. 
Unfortunately, there's not quite enough magic in there for my needs... now to 
find an affordable SMP Alpha system....

Thanks again,


Matt Nelson wrote:

> I am about to embark on a data processing software project that will 
> require a LOT of memory (about, ohhh, 6GB or so), and I was wondering if 
> there are any limitations to how one can use very large chunks of memory 
> under Linux. 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
> will be buffering a stream of data, then performing a variety of 
> calculations on large blocks of data at a time, before writing it out to 
> a socket.
> 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.
> I haven't seen this specifcally addressed, so I figured I should ask you 
> folk. Any insights/comments/reccomendations would be greatly appreciated.
> Thanks,
> Matt

Matthew Nelson
Dynamics Technology, Inc.
21311 Hawthorne Blvd., Suite 300, Torrance, CA 90503-5610
Voice: (310) 543-5433   FAX: (310) 543-2117   Email:

  parent reply	other threads:[~2001-06-12 14:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12  0:18 Any limitations on bigmem usage? Matt Nelson
2001-06-12  0:31 ` Doug McNaught
2001-06-12  0:38   ` Doug McNaught
2001-06-12 14:03 ` Matt Nelson [this message]
2001-06-12 16:29 ` Alan Cox
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 \ \ \ \

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