public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Kurktchiev <techstuff@gmx.net>
To: vda@port.imtp.ilyichevsk.odessa.ua, linux-kernel@vger.kernel.org
Subject: Re: Posible memory leak!?
Date: Thu, 15 May 2003 10:24:36 -0400	[thread overview]
Message-ID: <200305151024.37040.techstuff@gmx.net> (raw)
In-Reply-To: <200305150545.h4F5j2u27109@Port.imtp.ilyichevsk.odessa.ua>

On Thursday May 15 2003 1:51 am, Denis Vlasenko wrote:
> On 14 May 2003 17:12, Boris Kurktchiev wrote:
> > heh this is very interesting.... top b n1 reports this:
> > top - 10:08:24 up 16:36,  2 users,  load average: 0.16, 0.19, 0.08
> > Tasks:  62 total,   1 running,  60 sleeping,   0 stopped,   1 zombie
> > Cpu(s):  12.3% user,   5.1% system,   0.0% nice,  82.6% idle
> > Mem:    385904k total,   381572k used,     4332k free,   137244k
> > buffers Swap:   128512k total,    20012k used,   108500k free,
> > 126168k cached
>
> Typical. So what makes you think kernel leaks memory?

well the fact that before my swap was never used, and now .... I need to 
transcode something so I can show you how all swap is being used and non of 
the RAM (thus making programs run much slower, as is the case with 
transcode).

> BTW, which version of procps do you have? Mine is 2.0.10,
> 2.0.11 already exists.

I believe I have 2.0.10.

> gkrellm must be subtracting something from MemTotal trying
> to account for fact that large part of RAM is used as a cache.
> You may consult its source.

No... I forgot to tell it to count cache and buffers... 

  reply	other threads:[~2003-05-15 14:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13 18:15 Posible memory leak!? Boris Kurktchiev
2003-05-14  6:56 ` Denis Vlasenko
2003-05-14 14:12   ` Boris Kurktchiev
2003-05-15  5:51     ` Denis Vlasenko
2003-05-15 14:24       ` Boris Kurktchiev [this message]
2003-05-16  8:48         ` Denis Vlasenko
2003-05-16  4:03   ` The kernel is miscalculating my RAM Boris Kurktchiev
2003-05-16  5:42     ` Chris Friesen
2003-05-16  6:48       ` Boris Kurktchiev
2003-05-16  6:50       ` Boris Kurktchiev
  -- strict thread matches above, loose matches on Subject: below --
2003-05-10  6:29 [RFC] new syscall to allow notification when arbitrary pids die Chris Friesen
2003-05-12  3:26 ` Chris Friesen
2003-05-12  3:32   ` Doug McNaught
2003-05-12  3:42     ` Posible memory leak!? Boris Kurktchiev
2003-05-12 11:17       ` Boris Kurktchiev
     [not found]         ` <200305131158.h4DBw2u30860@Port.imtp.ilyichevsk.odessa.ua>
2003-05-13 18:17           ` Boris Kurktchiev
2003-05-12 18:06       ` Greg KH

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=200305151024.37040.techstuff@gmx.net \
    --to=techstuff@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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