From: "Buddy Lumpkin" <b.lumpkin@attbi.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Austin Gonyou" <austin@digitalroadkill.net>,
<vda@port.imtp.ilyichevsk.odessa.ua>,
"Ville Herva" <vherva@niksula.hut.fi>,
"DervishD" <raul@pleyades.net>,
"Linux-kernel" <linux-kernel@vger.kernel.org>
Subject: RE: About the need of a swap area
Date: Sat, 27 Jul 2002 16:01:05 -0700 [thread overview]
Message-ID: <FJEIKLCALBJLPMEOOMECCEPJCPAA.b.lumpkin@attbi.com> (raw)
In-Reply-To: <1027814596.21511.5.camel@irongate.swansea.linux.org.uk>
>> Why would you want to push *anything* to swap until you have to?
>To reduce the amount of disk access
So in Solaris, the scanner is going to eventually wake up as long as your
doing filesystem I/O, it's just a question of how long it takes to reach
lotsfree.
During that time it caches anything and everything in physical memory.
Are you implying that it should be looking for pages to swap out this whole
time to free up more space for filesystem and executable pages purely based
on lru? Have you done testing to prove that this is a better approach than
setting a threshold of when to wake up the lru mechanism?
>> Dirty filesystem pages have to be flushed to disk, it's just a question
of
>Clean ones do not. Dirty ones are also copied to disk but remain in
>memory for reread events. They may also be deleted before being written.
Solaris keeps dirty pages after they have been flushed to their backing
store, it's just when the system has to choose something to flush that it
preferences filesystem over anonymous and executable, what's wrong with
that?
>> and it's pretty relative what "long unaccessed" means ..
>In the Linux case the page cache is basically not discriminating too
>much about what page is (and it may be several things at once - cache,
>executing code and file data) just its access history.
Interesting ...
next prev parent reply other threads:[~2002-07-27 22:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 12:22 DervishD
2002-07-27 14:42 ` Ville Herva
2002-07-27 15:47 ` Rik van Riel
2002-07-27 20:41 ` Buddy Lumpkin
2002-07-27 20:50 ` Rik van Riel
2002-07-27 16:11 ` DervishD
2002-07-27 17:01 ` Ville Herva
2002-07-28 11:04 ` DervishD
2002-07-29 13:14 ` [lkml] " Ian Soboroff
2002-07-28 0:02 ` Denis Vlasenko
2002-07-27 20:58 ` Austin Gonyou
2002-07-27 22:22 ` Buddy Lumpkin
2002-07-27 23:40 ` Alan Cox
2002-07-27 22:35 ` Rik van Riel
2002-07-27 22:49 ` Buddy Lumpkin
2002-07-27 23:36 ` Daniel Phillips
2002-07-27 22:39 ` Buddy Lumpkin
2002-07-28 0:03 ` Alan Cox
2002-07-27 22:52 ` Rik van Riel
2002-07-27 23:01 ` Buddy Lumpkin [this message]
2002-07-28 0:28 ` Alan Cox
2002-07-27 23:34 ` Buddy Lumpkin
2002-07-28 6:58 ` Ville Herva
2002-07-28 7:59 ` Buddy Lumpkin
2002-07-28 8:19 ` Ville Herva
2002-07-28 14:11 ` Rik van Riel
2002-07-28 15:57 ` Ville Herva
2002-07-28 18:48 ` Buddy Lumpkin
2002-07-28 18:58 ` Ed Sweetman
2002-07-28 19:29 ` Rik van Riel
2002-07-28 19:47 ` Ed Sweetman
2002-07-28 20:42 ` Buddy Lumpkin
2002-07-28 20:27 ` Ville Herva
2002-07-30 19:31 ` Andy Isaacson
2002-07-28 16:20 ` Austin Gonyou
2002-07-29 7:18 ` Val Henson
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=FJEIKLCALBJLPMEOOMECCEPJCPAA.b.lumpkin@attbi.com \
--to=b.lumpkin@attbi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=austin@digitalroadkill.net \
--cc=linux-kernel@vger.kernel.org \
--cc=raul@pleyades.net \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=vherva@niksula.hut.fi \
/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®