mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Mark Knecht <markknecht@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	Daniel Walker <dwalker@mvista.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Latency data - 2.6.14-rc3-rt13
Date: Wed, 12 Oct 2005 02:38:51 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0510120233300.5830@localhost.localdomain> (raw)
In-Reply-To: <1129080062.7094.7.camel@mindpipe>


On Tue, 11 Oct 2005, Lee Revell wrote:

> On Tue, 2005-10-11 at 18:09 -0700, Mark Knecht wrote:
> > Should free memory drop like that over time?
>
> Yes this is perfectly normal.  When a system first boots all the memory
> your apps aren't using is initially free.  As applications access more
> data over time then it will be cached in memory until free memory drops
> to near zero.
>
> "Free memory" is actually wasted memory - it's better to use all
> available RAM for caching.
>

But the swap being touched bothers me.  Although I've had problems with
leaving Mozilla up for long times and it leaking. Without Mozilla running
and running lots of other apps, I have almost 100% memory used, but 0%
swap.

If the swap starts to increase slowly over time, you _do_ have a
leak somewhere.  Probably not in the kernel (kernel memory never goes into
swap). But if you want to see if the kernel is leaking, examine
/proc/slabinfo once in a while and if you see something there constantly
growing, then that might indicate a leak.  Just pay attention to the first
column.

-- Steve


  parent reply	other threads:[~2005-10-12  6:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-10 20:16 Mark Knecht
2005-10-10 20:49 ` Daniel Walker
2005-10-10 21:12   ` Mark Knecht
2005-10-10 21:28     ` Mark Knecht
2005-10-10 21:44       ` Daniel Walker
2005-10-10 22:09         ` Mark Knecht
2005-10-10 22:28           ` Daniel Walker
2005-10-10 23:33             ` Mark Knecht
2005-10-10 23:49               ` Mark Knecht
2005-10-11  3:45                 ` Mark Knecht
2005-10-11  6:46                   ` Steven Rostedt
2005-10-11  8:56                   ` Sven-Thorsten Dietrich
2005-10-11 11:17                   ` Ingo Molnar
2005-10-11 22:45                     ` Mark Knecht
2005-10-12  0:02                       ` Lee Revell
2005-10-12  1:09                         ` Mark Knecht
2005-10-12  1:21                           ` Lee Revell
2005-10-12  1:25                             ` Mark Knecht
2005-10-12  6:38                             ` Steven Rostedt [this message]
2005-10-12 16:18                               ` Lee Revell
2005-10-12 17:03                                 ` Steven Rostedt
2005-10-11  3:56                 ` Matan Peled
2005-10-11  4:45                   ` Mark Knecht
2005-10-11  6:14                     ` Ingo Molnar
2005-10-11  7:53                       ` Ingo Molnar
2005-10-10 21:39     ` Daniel Walker

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.58.0510120233300.5830@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markknecht@gmail.com \
    --cc=mingo@elte.hu \
    --cc=rlrevell@joe-job.com \
    /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®