From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel cached memory
Date: Mon, 25 Jul 2005 23:03:06 -0600 [thread overview]
Message-ID: <42E5C40A.7000709@shaw.ca> (raw)
In-Reply-To: <4tdIU-479-9@gated-at.bofh.it>
John Pearson wrote:
> Wouldn't having (practically) all your memory used for cache slow down
> starting a new program? First it would have to free up that space, and then
> put stuff in that space, taking potentially twice as long.
If the cache pages are clean (not been modified since they were read
from the disk), then evicting that data will not take very long. If the
program you are just starting is not in the cache, then the time taken
to load it from disk will dwarf the time needed to evict cached pages.
And there's also the possibility that the cache contains the data you
are loading, which definitely will speed things up..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2005-07-26 5:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4t5s8-68A-33@gated-at.bofh.it>
[not found] ` <4tdIU-479-9@gated-at.bofh.it>
2005-07-26 5:03 ` Robert Hancock [this message]
2005-07-26 15:00 ` Kernel cached memory Bill Davidsen
2005-07-26 0:35 Chuck Ebbert
-- strict thread matches above, loose matches on Subject: below --
2005-07-22 9:46 Ashley
2005-07-22 11:31 ` Diego Calleja
2005-07-22 12:57 ` Erik Mouw
2005-07-22 21:43 ` John Pearson
2005-07-23 12:31 ` Denis Vlasenko
2005-07-22 13:25 ` Gábor Lénárt
2005-07-22 17:58 ` Lee Revell
2005-07-23 10:50 ` Oliver Neukum
2005-07-25 16:47 ` Bill Davidsen
2005-07-25 17:03 ` Diego Calleja
2005-07-25 17:07 ` Paolo Ornati
2005-07-25 18:02 ` Bill Davidsen
2005-08-01 10:38 ` Gábor Lénárt
2005-08-01 21:08 ` Bill Davidsen
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=42E5C40A.7000709@shaw.ca \
--to=hancockr@shaw.ca \
--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