From: Andi Kleen <ak@suse.de>
To: "Ian S. Nelson" <ian.nelson@echostar.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: How come top and /proc/meminfo on 2.4.0 says 0K shared?
Date: Fri, 19 Jan 2001 17:46:08 +0100 [thread overview]
Message-ID: <20010119174608.A22956@gruyere.muc.suse.de> (raw)
In-Reply-To: <3A686DB1.8096DA0D@echostar.com>
In-Reply-To: <3A686DB1.8096DA0D@echostar.com>; from ian.nelson@echostar.com on Fri, Jan 19, 2001 at 09:39:13AM -0700
On Fri, Jan 19, 2001 at 09:39:13AM -0700, Ian S. Nelson wrote:
> is this a bug?
>
> We have a number of machines running 2.4.0 and /proc/meminfo says we're
> sharing no memory. top says that also, probably because it just reads
> /proc/meminfo, or at least I assume that's how it works. All the
> individual procs show the memory they are sharing though.
It has been removed because the computation involved walking the complete
memory maps and it caused noticeable scheduling hickups (mouse pointer hangs etc.)
on big memory machines.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-19 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 16:39 Ian S. Nelson
2001-01-19 16:46 ` Andi Kleen [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=20010119174608.A22956@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=ian.nelson@echostar.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®