From: Daniel Gryniewicz <dang@fprintf.net>
To: James A Sutherland <jas88@cam.ac.uk>
Cc: war@starband.net, oliver@neukum.org, linux-kernel@vger.kernel.org
Subject: Re: Swap vs No Swap.
Date: Fri, 23 Nov 2001 17:05:20 -0500 [thread overview]
Message-ID: <20011123170520.2276b8be.dang@fprintf.net> (raw)
In-Reply-To: <E166wSm-00063a-00@mauve.csi.cam.ac.uk>
In-Reply-To: <3BFC5A9B.915B77DF@starband.net> <01112211150302.00690@argo> <3BFD214F.36A55D94@starband.net> <E166wSm-00063a-00@mauve.csi.cam.ac.uk>
On Thu, 22 Nov 2001 16:12:32 +0000
James A Sutherland <jas88@cam.ac.uk> wrote:
> "when it swaps" is meaningless: Linux ALWAYS swaps when there is swapspace.
> Do you mean when it *thrashes*? Or does your system have problems during I/O
> such as not using DMA for disk access?
[17:03 athena] dang> free
total used free shared buffers cached
Mem: 255304 184416 70888 716 12636 77524
-/+ buffers/cache: 94256 161048
Swap: 128484 0 128484
[17:03 athena] dang> uname -a
Linux athena.fprintf.net 2.4.13-ac7-preempt-sse #1 Mon Nov 5 14:06:53 EST 2001
i686 unknown
[17:04 athena] dang>
Linux does not always swap.
Daniel
---
Recursion n.:
See Recursion.
-- Random Shack Data Processing Dictionary
next prev parent reply other threads:[~2001-11-23 22:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 1:53 Swap vs No Swap war
2001-11-22 2:23 ` Joel Jaeggli
2001-11-22 2:31 ` war
2001-11-22 2:58 ` Mark Hahn
2001-11-22 4:09 ` listmail
2001-11-22 5:24 ` H. Peter Anvin
2001-11-22 5:30 ` war
2001-11-22 5:32 ` H. Peter Anvin
2001-11-22 9:50 ` Christian Bornträger
2001-11-22 8:50 ` Rik van Riel
2001-11-22 11:00 ` James A Sutherland
2001-11-22 16:00 ` war
2001-11-22 16:08 ` James A Sutherland
2001-11-22 16:57 ` Rik van Riel
2001-11-22 18:56 ` François Cami
2001-11-22 18:58 ` James A Sutherland
2001-11-22 19:17 ` François Cami
2001-11-22 19:36 ` G . Sumner Hayes
2001-11-22 20:37 ` James A Sutherland
2001-11-23 6:30 ` Charles Marslett
2001-11-23 9:13 ` James A Sutherland
2001-11-23 16:46 ` Charles Marslett
2001-11-22 16:25 ` war
2001-11-22 16:37 ` Ryan Cumming
2001-11-22 17:39 ` James A Sutherland
2001-11-22 17:56 ` war
[not found] ` <01112211150302.00690@argo>
2001-11-22 16:01 ` war
2001-11-22 16:12 ` James A Sutherland
2001-11-22 16:36 ` war
2001-11-22 16:33 ` Bjorn Wesen
2001-11-22 17:37 ` Thomas S. Iversen
2001-11-22 21:18 ` Mike Galbraith
2001-11-22 17:41 ` James A Sutherland
2001-11-22 17:56 ` war
2001-11-22 18:08 ` James A Sutherland
2001-11-23 22:05 ` Daniel Gryniewicz [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-22 16:11 Elgar, Jeremy
2001-11-22 16:22 ` Ryan Cumming
2001-11-22 16:22 ` Stephan von Krawczynski
2001-11-22 16:29 Elgar, Jeremy
[not found] <Pine.LNX.4.10.10111221006010.29736-100000@coffee.psychology.mcmaster.ca>
2001-11-22 16:34 ` war
2001-11-26 20:18 ` Kent Borg
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=20011123170520.2276b8be.dang@fprintf.net \
--to=dang@fprintf.net \
--cc=jas88@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=war@starband.net \
/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