mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: space-00002@vortex.physik.uni-konstanz.de
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@zip.com.au>
Subject: Re: buffer/memory strangeness in 2.4.16 / 2.4.17pre2
Date: Sat, 1 Dec 2001 23:07:19 +0100	[thread overview]
Message-ID: <200112012209.fB1M92s12294@vortex.physik.uni-konstanz.de> (raw)
In-Reply-To: <200111291201.fATC1pd04206@lists.us.dell.com> <200111292030.fATKU1s05921@vortex.physik.uni-konstanz.de> <3C075196.613894EA@zip.com.au>
In-Reply-To: <3C075196.613894EA@zip.com.au>

It is still the same in 2.4.17pre2 :-(

On Friday 30 November 2001 10:29, Andrew Morton wrote:
> space-00002@vortex.physik.uni-konstanz.de wrote:
> > Hi,
> >
> > I am experiencing a bit of strange system behaviour in a vanilla 2.4.16
> > kernel (2.95.3, very stable machine etc.)
> >
> > I noticed, that after running for a while (day) I had significantly less
> > memory available for my simulation program than right after booting.
> > Looking at the problem using 'xosview' (or 'free'), I noticed that there
> > was a large number of MBs filled with 'buffers' that did not get wiped
> > when other programs need the memory. The system seems to rather kill an
> > 'offender' than clean out buffers.
>
> Seconded.   After an updatedb run, my 768 megabyte 2.5.1-pre4 machine
> shows:
>
>              total       used       free     shared    buffers     cached
> Mem:        770668     384460     386208          0     138548      17744
> -/+ buffers/cache:     228168     542500
>
> and, after malloc/memset of 700 megs:
>
>              total       used       free     shared    buffers     cached
> Mem:        770668      73340     697328          0      41160       5960
> -/+ buffers/cache:      26220     744448
> Swap:       499928      18628     481300
>
> I repeated the malloc/memset a few times, wrote a gigabyte file
> and was unable to make the 40 megabytes of buffermem go away.
>
> MemTotal:       770668 kB
> MemFree:        698008 kB
> MemShared:           0 kB
> Buffers:         42092 kB
> Cached:           6088 kB
> SwapCached:       9808 kB
> Active:          48064 kB
> Inactive:        10112 kB
> HighTotal:           0 kB
> HighFree:            0 kB
> LowTotal:       770668 kB
> LowFree:        698008 kB
> SwapTotal:      499928 kB
> SwapFree:       484512 kB
>
> After running an extremely memory-intensive test program for
> two minutes, buffermem fell to 38 megabytes.
>
> Seems broken to me.

  reply	other threads:[~2001-12-01 22:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200111291201.fATC1pd04206@lists.us.dell.com>
2001-11-29 20:39 ` buffer/memory strangeness in 2.4.16 space-00002
2001-11-30  9:29   ` Andrew Morton
2001-12-01 22:07     ` space-00002 [this message]
2001-12-02  4:43       ` buffer/memory strangeness in 2.4.16 / 2.4.17pre2 Andrew Morton
2001-12-02 12:17         ` Rik van Riel
2001-12-02 17:08           ` space-00002
2001-12-14  1:30 ` buffer/memory strangeness in 2.4.16; fixed in 2.4.17-rc1 space-00002

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=200112012209.fB1M92s12294@vortex.physik.uni-konstanz.de \
    --to=space-00002@vortex.physik.uni-konstanz.de \
    --cc=akpm@zip.com.au \
    --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®