From: Ian Stirling <tandra@mauve.plus.com>
To: Valdis.Kletnieks@vt.edu
Cc: yunfeng zhang <zyf.zeroos@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Improvement on memory subsystem
Date: Wed, 19 Jul 2006 10:18:44 +0100 [thread overview]
Message-ID: <44BDF8F4.30908@mauve.plus.com> (raw)
In-Reply-To: <200607181218.k6ICIgeS027067@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Tue, 18 Jul 2006 18:03:54 +0800, yunfeng zhang said:
>
>
>>2. Read-ahead process during page-in/out (page fault or swap out) should be
>>based on its VMA to enhance IO efficiency instead of the relative physical pages
>>in swap space.
>
>
> But wouldn't that end up causing a seek storm, rather than handling the pages
> in the order that minimizes the total seek distance, no matter where they are
> in memory? Remember - if you have a 2Ghz processor, and a disk that seeks in 1
> millisecond, every seek is (*very* roughly) about 2 million instructions. So
> if we can burn 20 thousand instructions finding a read order that eliminates
> *one* seek, we're 1.98M instructions ahead.
To paraphrase shakespear - all the world is not a P4 - and all the swap
devices are not hard disks.
For example - I've got a 486/33 laptop with 12M RAM that I sometimes use
, with swapping to a 128M PCMCIA RAM card that I got from somewhere.
20K instructions wasted on a device with no seek time is just annoying.
And on my main laptop - I have experimented with swap-over-wifi to a
large ramdisk on my server - which works quite well. (until the wifi
connection falls over).
next prev parent reply other threads:[~2006-07-19 9:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 10:03 yunfeng zhang
2006-07-18 12:18 ` Valdis.Kletnieks
2006-07-19 3:44 ` yunfeng zhang
2006-07-19 9:18 ` Ian Stirling [this message]
2006-07-19 14:56 ` Valdis.Kletnieks
2006-07-18 16:25 ` Pekka Enberg
2006-07-19 3:21 ` yunfeng zhang
2006-07-19 8:30 ` Pekka Enberg
2006-07-19 10:13 ` yunfeng zhang
2006-07-19 10:35 ` Pekka Enberg
2006-07-24 9:01 ` yunfeng zhang
2006-07-24 14:55 ` David Lang
2006-07-25 8:33 ` yunfeng zhang
2006-08-23 10:39 ` yunfeng zhang
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=44BDF8F4.30908@mauve.plus.com \
--to=tandra@mauve.plus.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=zyf.zeroos@gmail.com \
/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
all inboxes | Powered by JetHome®