The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Memory accounting problem in 2.4.13, 2.4.14pre, and possibly 2.4.14
Date: Wed, 7 Nov 2001 13:36:44 -0800	[thread overview]
Message-ID: <20011107133644.D20245@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011106140335.A13678@mikef-linux.matchmail.com>
In-Reply-To: <20011106140335.A13678@mikef-linux.matchmail.com>

On Tue, Nov 06, 2001 at 02:03:35PM -0800, Mike Fedyk wrote:
> Hello,
> 
> I am trying to track down a memory accounting problem I've seen ever since I
> tried a 2.4.13 based kernel.  Specifically I've noticed an overflow for the
> "Cached" entry in /proc/meminfo, but also the numbers don't add up to the
> total memory count.  Shouldn't they add up?  If they should, I haven't seen
> one that does....
> 
> I first noticed it on:
> 2.4.13freeswan-1.91+ac5+preempt+netdev_random+vm_freeswap
> 2.4.14-pre6+preempt+netdev_random+ext3_0.9.14-2414p5
> 
> I thought it may be preempt so I tried:
> 2.4.14-pre8+netdev_random-p7+xsched+ext3_0.9.14-2414p8+elevator
> 
> But I still get the same problem with "Cached".
> 
> Now I'm trying to see if it could be ext3 with:
> 2.4.14-ext3-2.4-0.9.14-2414p8
> 
> And I haven't noticed the problem after 16 hours uptime.  Sometimes it would
> show earlier, or later.
> 
> >From current (2.4.14-ext3-2.4-0.9.14-2414p8) kernel:
>         total:    used:    free:  shared: buffers:  cached:
> Mem:  261443584 254337024  7106560        0 58957824 76398592
> Swap: 199815168  1228800 198586368
> MemTotal:       255316 kB
> MemFree:          6940 kB
> MemShared:           0 kB
> Buffers:         57576 kB
> Cached:          73408 kB
> SwapCached:       1200 kB
> Active:          65048 kB
> Inactive:       138040 kB
> HighTotal:           0 kB
> HighFree:            0 kB
> LowTotal:       255316 kB
> LowFree:          6940 kB
> SwapTotal:      195132 kB
> SwapFree:       193932 kB
> 
> Subtracted from MemTotal should = 0:
> MemFree:          6940 kB
> Active:          65048 kB
> Inactive:       138040 kB
> = 45288 kB remaining
> 
> Shouldn't these numbers add up to MemTotal?
> 
> $ dpkg -l "*gcc*"|grep ii
> ii  gcc            2.95.4-8       The GNU C compiler.
> ii  gcc-2.95       2.95.4-0.01100 The GNU C compiler.
> 
> On Debian Sid.
> 
> I can provide more information upon request...
> 

To continue the results...

Now  : 1 day(s), 15:47:31 running Linux 2.4.14-ext3-2.4-0.9.14-2414p8

has also exibited the problem with cached.

I'm going to try unpatched 2.4.14 now...

Mike

  reply	other threads:[~2001-11-07 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06 22:03 Memory accounting problem in 2.4.13, 2.4.14pre, and possibly 2.4.14 Mike Fedyk
2001-11-07 21:36 ` Mike Fedyk [this message]
2001-11-08  1:30   ` Mike Fedyk
2001-11-08  2:10 ` Andrew Morton
2001-11-08  2:24   ` Mike Fedyk
2001-11-08  5:00     ` Andrew Morton
2001-11-08  6:47       ` Mike Fedyk
2001-11-08 14:41       ` James Bourne

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=20011107133644.D20245@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.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