From: Robert Hancock <hancockr@shaw.ca>
To: "Mouawad, Tony" <Tony.Mouawad@christiedigital.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help Understanding Linux memory management
Date: Tue, 10 Apr 2007 08:15:09 -0600 [thread overview]
Message-ID: <461B9BED.6030208@shaw.ca> (raw)
In-Reply-To: <fa.jFpt5NWxHc2YH0jy7hPsDxyUr0E@ifi.uio.no>
Mouawad, Tony wrote:
> Hello,
>
> I've been a MS Windows based programmer for a very long time and was
> recently tossed in an environment where I am developing embedded apps on
> the m68k / Linux platform. That makes me a Linux newbie. I started
> asking a few questions on various IRC channels and was directed to this
> group. So, I will start asking:
>
> These are questions derived from observations on the MCF 5475 CPU
> running Linux 2.6.10 built for the m68k platform. Disk swapping is
> disabled.
>
> 1) When physical memory runs low, the memory manager will try to use
> memory currently allocated to the pagecache. Is this true?
Yes.
> 2) When vm.overcommit_memory = 2 (overcommit disabled), and memory runs
> low, it appears that the memory manager does not try to use memory
> currently allocated to pagecache. Is this true?
Shouldn't be, what makes you think this is happening?
> 3) Is it possible to disable the pagecache?
Not as far as I know, it's unlikely this would be of any benefit.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-04-10 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.jFpt5NWxHc2YH0jy7hPsDxyUr0E@ifi.uio.no>
2007-04-10 14:15 ` Robert Hancock [this message]
2007-04-10 14:31 ` Help Understanding Linux memory management Mouawad, Tony
2007-04-10 16:16 ` Alan Cox
2007-04-10 18:17 ` Mouawad, Tony
2007-04-10 13:51 Mouawad, Tony
2007-04-10 14:22 ` Laurent Pinchart
2007-04-12 0:23 ` David Schwartz
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=461B9BED.6030208@shaw.ca \
--to=hancockr@shaw.ca \
--cc=Tony.Mouawad@christiedigital.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox