mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Nix <nix@esperi.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10: SPARC64 mapped figure goes unsignedly negative...
Date: Mon, 31 Jan 2005 17:06:29 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0501311642400.6072@goblin.wat.veritas.com> (raw)
In-Reply-To: <87d5vlwp8k.fsf@amaterasu.srvr.nix>

On Mon, 31 Jan 2005, Nix wrote:
> 
> Odd: this machine seems to be using swap, albeit not very much (and I've
> got the swap priorities upside down, as well; whoops, that's probably
> been harming performance for, well, years):
> 
> 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.
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.

> I'll build rmap.c with GCC-3.3 later tonight (if I can find a copy on my
> old backups), compare the generated code, and see if anything leaps out
> at me.

Worth doing, thank you.  Rene has sent us the GCC-3.4 output,
but I've not spotted anything the matter with it yet.

Hugh

  reply	other threads:[~2005-01-31 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30 17:04 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 [this message]
2005-01-31 17:31           ` Nix

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=Pine.LNX.4.61.0501311642400.6072@goblin.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix@esperi.org.uk \
    /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®