From: John Fremlin <vii@users.sourceforge.net>
To: Jason McMullan <jmcmullan@linuxcare.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: VM Requirement Document - v0.0
Date: 28 Jun 2001 23:47:53 +0100 [thread overview]
Message-ID: <m24rt0gr1i.fsf@boreas.yi.org.> (raw)
In-Reply-To: <20010626155838.A23098@jmcmullan.resilience.com> (Jason McMullan's message of "Tue, 26 Jun 2001 15:58:38 -0400")
[...]
> immediate: RAM, on-chip cache, etc.
> fast: Flash reads, ROMs, etc.
> medium: Hard drives, CD-ROMs, 100Mb ethernet, etc.
> slow: Flash writes, floppy disks, CD-WR burners
> packeted: Reads/write should be in as large a packet as possible
>
> Embedded Case
[...]
> Desktop Case
I'm not sure there's any point in separating the cases like this. The
complex part of the VM is the caching part => to be a good cache you
must take into account the speed of accesses to the cached medium,
including warm up times for sleepy drives etc.
It would be really cool if the VM could do that, so e.g. in the ideal
world you could connect up a slow harddrive and have its contents
cached as swap on your fast harddrive(!) (not a new idea btw and
already implemented elsewhere). I.e. from the point of view of the VM a
computer is just a group of data storage units and it's allowed to use
up certain parts of each one to do stuff
[...]
--
http://ape.n3.net
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
parent reply other threads:[~2001-06-28 22:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20010626155838.A23098@jmcmullan.resilience.com>]
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=m24rt0gr1i.fsf@boreas.yi.org. \
--to=vii@users.sourceforge.net \
--cc=jmcmullan@linuxcare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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