LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Raz Ben-Jehuda(caro)" <raziebe@gmail.com>
To: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: [DISCUSS] memory allocation method
Date: Mon, 15 Jan 2007 15:36:41 +0200	[thread overview]
Message-ID: <5d96567b0701150536j4c3c50abndec5155ddb53d4a1@mail.gmail.com> (raw)

I have a process who allocates as much as possible of RAM
in 4 G ram 32bit machine.  This buffer is never released.

Questions:

1. Is it better allocates with many 1MB buffers or allocate it in with
one a big valloc ?

2. I will be needing to make this memory allocation in many other
machines , some have 2 GRAM and some 3 GRAM. what is the preferrable
method  ?

3. In 64bit machines , is it possible to allocate huge buffers , such
as 30 GB of ram ?

Thank you
-- 
Raz

             reply	other threads:[~2007-01-15 13:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15 13:36 Raz Ben-Jehuda(caro) [this message]
2007-01-19 10:41 ` Helge Hafting
2007-01-19 11:42 ` Rick Brown

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=5d96567b0701150536j4c3c50abndec5155ddb53d4a1@mail.gmail.com \
    --to=raziebe@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [DISCUSS] memory allocation method' \
    /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

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