All of
 help / color / mirror / Atom feed
From: Rik van Riel <>
To: Vinay I K <>
Subject: Re: Linux free issue
Date: Sat, 19 Jul 2003 10:39:04 -0400 (EDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, 19 Jul 2003, Vinay I K wrote:

> I am a bit confused. When we call free in Linux, is the memory not given
> back to the system(just cached)? What is the state of the issue in the
> latest Linux Kernel?

The issue is not in the Linux kernel at all, but in glibc.
It is the C library that has (after careful measuring and
optimising) made the decision to not call the system call
to free memory but instead keep it for later use.

I suspect their decision is the right one in most of the

To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to  For more info on Linux MM,
see: .
Don't email: <a href=mailto:""> </a>

  reply	other threads:[~2003-07-19 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-19 13:34 Linux free issue Vinay I K
2003-07-19 14:39 ` Rik van Riel [this message]
2003-07-20  2:27   ` Eugene Teo
2003-07-19 13:35 Vinay I K

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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.