ok, first off let's not turn this into a *ix vs. *ix type discussion, I
didn't mean to imply Solaris is more superior.
But that's exactly what it does. Solaris doesn't move *anything* to swap
until you reach a watermark called cachefree (which may or may not be equal
to lotsfree)
Why would you want to push *anything* to swap until you have to?
Dirty filesystem pages have to be flushed to disk, it's just a question of
when. Why on earth would I ever decide to move anonymous pages for any
process to disk if I can flush dirty pages to their backing store and put
non-dirty filesystem pages back on the freelist?
Like I said, it's very rare for my systems to do any I/O to swap at all.
and it's pretty relative what "long unaccessed" means ..
--Buddy
-----Original Message-----
From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
Sent: Saturday, July 27, 2002 4:40 PM
To: Buddy Lumpkin
Cc: Austin Gonyou; vda@port.imtp.ilyichevsk.odessa.ua; Ville Herva;
DervishD; Linux-kernel
Subject: RE: About the need of a swap area
On Sat, 2002-07-27 at 23:22, Buddy Lumpkin wrote:
> I thought linux worked more like Solaris where it didn't use any swap (AT
> ALL) until it has to... At least, I hope linux works this way.
I'd be suprised if Solaris did something that dumb.
You want to push out old long unaccessed pages of code to make room for
more cached disk blocks from files.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jul 30 2002 - 14:00:27 EST