mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 15:39:41 -0700	[thread overview]
Message-ID: <FJEIKLCALBJLPMEOOMECOEPGCPAA.b.lumpkin@attbi.com> (raw)
In-Reply-To: <1027813211.21516.2.camel@irongate.swansea.linux.org.uk>

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.



  parent reply	other threads:[~2002-07-27 22:35 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 [this message]
2002-07-28  0:03             ` Alan Cox
2002-07-27 22:52               ` Rik van Riel
2002-07-27 23:01               ` Buddy Lumpkin
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=FJEIKLCALBJLPMEOOMECOEPGCPAA.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®