From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: About _real_ free memory
Date: Thu, 16 Oct 2003 09:48:30 +0200 [thread overview]
Message-ID: <yw1xsmltaai9.fsf@users.sourceforge.net> (raw)
In-Reply-To: D9B4591FDBACD411B01E00508BB33C1B01F6EA74@mesadm.epl.prov-liege.be
"Frederick, Fabian" <Fabian.Frederick@prov-liege.be> writes:
> Is there a way to clean cache from unwanted data or something to
> unlink the stuff and regain some more 'free' mem. ?
If a process tries to allocate and use more than the really free
amount, some cache will be dropped automatically. From a performance
point of view, this could of course be undesirable, but normally
there's no need to think about it.
--
Måns Rullgård
mru@users.sf.net
next prev parent reply other threads:[~2003-10-16 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 7:23 About _real_ free memory Frederick, Fabian
2003-10-16 7:48 ` Måns Rullgård [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-16 9:04 Frederick, Fabian
2003-10-16 11:44 ` Jakob Oestergaard
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=yw1xsmltaai9.fsf@users.sourceforge.net \
--to=mru@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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
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.