From: Lee Revell <rlrevell@joe-job.com>
To: davids@webmaster.com
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
"'Ankit Jain'" <ankitjain1580@yahoo.com>
Subject: RE: VM Vs Swap Space
Date: Thu, 14 Oct 2004 00:09:50 -0400 [thread overview]
Message-ID: <1097726989.2682.3.camel@krustophenia.net> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKOEMJOPAA.davids@webmaster.com>
On Wed, 2004-10-13 at 19:35, David Schwartz wrote:
> > A long but basic explanation of the difference between "Virtual
> > Memory" and "Swap
> > Space" follows:
>
> One of the problems with a 'basic' explanation is that you always wind up
> leaving out something that someone else things is important. ;)
>
"Unix Internals" by Uresh Vahalia is the best book on the subject I know
of. You could never explain virtual memory in a single mailing list
thread...
Lee
prev parent reply other threads:[~2004-10-14 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 9:17 Ankit Jain
2004-10-07 19:30 ` Rik van Riel
2004-10-13 22:46 ` Robert White
2004-10-13 23:35 ` David Schwartz
2004-10-14 4:09 ` Lee Revell [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=1097726989.2682.3.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=ankitjain1580@yahoo.com \
--cc=davids@webmaster.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
Powered by JetHome