From: Nix <nix@esperi.org.uk>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10: SPARC64 mapped figure goes unsignedly negative...
Date: Mon, 31 Jan 2005 17:31:04 +0000 [thread overview]
Message-ID: <87vf9dv73b.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <Pine.LNX.4.61.0501311642400.6072@goblin.wat.veritas.com> (Hugh Dickins's message of "Mon, 31 Jan 2005 17:06:29 +0000 (GMT)")
On Mon, 31 Jan 2005, Hugh Dickins uttered the following:
> On Mon, 31 Jan 2005, Nix wrote:
>> Filename Type Size Used Priority
>> /dev/sda2 partition 523016 0 1
>> /dev/sda4 partition 511232 57648 2
>> /dev/sdb2 partition 523016 0 1
>>
>> Is the problem that the higher-priority kicking out to swap which should
>> happen when memory is tight, won't?
>
> I had thought that it was any kicking out to swap - apart from kicking
> tmpfs/shmem pages to swap, which should happen independently of Mapped.
>
> If you're not using tmpfs or shmem, then I'm surprised by that figure.
Oh. Yes, tmpfs might just about explain it:
58320 /tmp
So it looks like I have a swap-free box for a time. I guess I'd better
be careful... :)
> There was 88 kB out to swap in your original /proc/meminfo, which we
> may suppose was before Mapped went negative; but above shows more since.
Yes, I expect so. It must've gone negative really rather early: and note
that it's some distance below 2^64 by now, so it's still falling. If I
wait for a billion years or so it might wrap around. :)
--
`Blish is clearly in love with language. Unfortunately,
language dislikes him intensely.' --- Russ Allbery
prev parent reply other threads:[~2005-01-31 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 17:04 2.6.10: SPARC64 mapped figure goes unsignedly negative Nix
2005-01-31 13:04 ` Hugh Dickins
2005-01-31 15:30 ` Nix
2005-01-31 16:01 ` Hugh Dickins
2005-01-31 16:13 ` Nix
2005-01-31 17:06 ` Hugh Dickins
2005-01-31 17:31 ` Nix [this message]
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=87vf9dv73b.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=hugh@veritas.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