From: Lucio de Re lucio@proxima.alt.za
Subject: [9fans] Plan 9 on PC - memory and swap
Date: Wed, 23 Jul 1997 15:05:21 +0200 [thread overview]
Message-ID: <19970723130521._3mqYL4_y8cr1jgiwmmni2xMjpZICbglQrEdFq9r3VA@z> (raw)
Loading a version of 9pccpudisk, I get the following message:
2531 free pages, 10124K bytes, swap 55564K, highwater 504K, headroom
628K
a "cat /dev/swap" yields:
641/2531 memory 0/11360 swap
on an idle CPU/auth server.
I've not bothered with the details before, but now I'm curious.
Evidently, the swap value in the kernel message is displayed
incorrectly, specially in view of the fact that swap has not been
enabled at the time the kernel loads.
Given that the CPU server has 16 meg of RAM, I'd also be curious as to
why only 2531K remains available. Pointers to reading material are
welcome.
--
Lucio de Re (lucio@proxima.alt.za)
Disclaimer: I'm working at getting my opinions to agree with me.
next reply other threads:[~1997-07-23 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-23 13:05 Lucio [this message]
1997-07-23 17:43 David
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=19970723130521._3mqYL4_y8cr1jgiwmmni2xMjpZICbglQrEdFq9r3VA@z \
--to=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).