From: Ville Herva <vherva@niksula.hut.fi>
To: Buddy Lumpkin <b.lumpkin@attbi.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: About the need of a swap area
Date: Sun, 28 Jul 2002 11:19:33 +0300 [thread overview]
Message-ID: <20020728081932.GV1548@niksula.cs.hut.fi> (raw)
In-Reply-To: <FJEIKLCALBJLPMEOOMECIEADDAAA.b.lumpkin@attbi.com>
On Sun, Jul 28, 2002 at 12:59:13AM -0700, you [Buddy Lumpkin] wrote:
>
> In Solaris you don't even need to define a swap device at all.
> If your sure that you will never reach lotsfree (for that matter, nothing
> stops you from setting lotsfree, desfree and minfree to whatever value you
> want) Solaris will happily run without a swap device even defined.
You don't have to have swap device in linux either (afaik it has never been
mandatory). Linux will run without swap just like you would expect.
> Once you reach the lotsfree watermark it's a whole different story, then it
> makes perfect sense to queue up writes to the swap device and write
> them out to swap in a sensible way as you point out above, but when I made
> the comment above, I was referring to a system that is not low on memory.
Obviously, if you have heaps of free memory, linux will not usually touch
swap either. The exact point where swap starts to get used is of course a
matter of debate (and depends on vm implementation and tunables in linux).
But the point is: even if there is no immediate memory pressure, backing
pages to swap is no crime.
-- v --
v@iki.fi
next prev parent reply other threads:[~2002-07-28 8:16 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
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 [this message]
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=20020728081932.GV1548@niksula.cs.hut.fi \
--to=vherva@niksula.hut.fi \
--cc=b.lumpkin@attbi.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®