LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Rick Brown" <rick.brown.3@gmail.com>
To: "Raz Ben-Jehuda(caro)" <raziebe@gmail.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [DISCUSS] memory allocation method
Date: Fri, 19 Jan 2007 17:12:35 +0530	[thread overview]
Message-ID: <7783925d0701190342j7e0e89a0ib0e9a7278887355f@mail.gmail.com> (raw)
In-Reply-To: <5d96567b0701150536j4c3c50abndec5155ddb53d4a1@mail.gmail.com>

On 1/15/07, Raz Ben-Jehuda(caro) <raziebe@gmail.com> wrote:
> 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 ?

ONe BIG vmalloc has huge, huge chances of failure.

      parent reply	other threads:[~2007-01-19 11:42 UTC|newest]

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

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=7783925d0701190342j7e0e89a0ib0e9a7278887355f@mail.gmail.com \
    --to=rick.brown.3@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raziebe@gmail.com \
    --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).