public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Blueman" <daniel.blueman@gmx.net>
To: linux-ia64@vger.kernel.org, davidm@napali.hpl.hp.com,
	linux-kernel@vger.kernel.org
Subject: [2.6.7, ia64] continual memory leak at ~102kB/s...
Date: Fri, 6 Aug 2004 16:44:18 +0200 (MEST)	[thread overview]
Message-ID: <20029.1091803458@www55.gmx.net> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 3854 bytes --]

When running 2.6.7 on a generic ia64 system, I see memory being leaked in
the kernel. Most of the fancy (preempt, hot-plug procs, ...) features are
disabled, and the system in a quiescent state [1].

/proc/meminfo shows the memory as unaccounted for [2], so it seems likely it
has been kmalloc()d somehere. A small script shows memory disappearing at
102kB/s [3].

Anyone else seen this on ia64?

--- [1]

# ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  1 10:29 ?        00:00:04 init [S]              
root         2     1  0 10:29 ?        00:00:00 [migration/0]
root         3     1  0 10:29 ?        00:00:00 [ksoftirqd/0]
root         4     1  0 10:29 ?        00:00:00 [migration/1]
root         5     1  0 10:29 ?        00:00:00 [ksoftirqd/1]
root         6     1  0 10:29 ?        00:00:00 [migration/2]
root         7     1  0 10:29 ?        00:00:00 [ksoftirqd/2]
root         8     1  0 10:29 ?        00:00:00 [migration/3]
root         9     1  0 10:29 ?        00:00:00 [ksoftirqd/3]
root        10     1  0 10:29 ?        00:00:00 [events/0]
root        11     1  0 10:29 ?        00:00:00 [events/1]
root        12     1  0 10:29 ?        00:00:00 [events/2]
root        13     1  0 10:29 ?        00:00:00 [events/3]
root        14    10  0 10:29 ?        00:00:00 [khelper]
root        15    10  0 10:29 ?        00:00:00 [kacpid]
root        70    10  0 10:29 ?        00:00:00 [kblockd/0]
root        71    10  0 10:29 ?        00:00:00 [kblockd/1]
root        72    10  0 10:29 ?        00:00:00 [kblockd/2]
root        73    10  0 10:29 ?        00:00:00 [kblockd/3]
root        83    10  0 10:29 ?        00:00:00 [pdflush]
root        84    10  0 10:29 ?        00:00:00 [pdflush]
root        85     1  0 10:29 ?        00:00:00 [kswapd0]
root        86    10  0 10:29 ?        00:00:00 [aio/0]
root        87    10  0 10:29 ?        00:00:00 [aio/1]
root        88    10  0 10:29 ?        00:00:00 [aio/2]
root        89    10  0 10:29 ?        00:00:00 [aio/3]
root       194     1  0 10:29 ?        00:00:00 [scsi_eh_0]
root       206     1  0 10:29 ?        00:00:00 [scsi_eh_1]
root       210     1  0 10:29 ?        00:00:00 [kjournald]
root       836     1  0 10:29 ttyS1    00:00:00 init [S]              
root       837   836  0 10:29 ttyS1    00:00:00 /bin/sh
root       846   837  0 10:33 ttyS1    00:00:00 ps -ef

--- [2]

# cat /proc/meminfo; sleep 10; cat /proc/meminfo
MemTotal:      1006272 kB
MemFree:        671104 kB
Buffers:         14720 kB
Cached:          18304 kB
SwapCached:          0 kB
Active:          35584 kB
Inactive:         9216 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      1006272 kB
LowFree:        671104 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:               0 kB
Writeback:           0 kB
Mapped:           6592 kB
Slab:           212160 kB
Committed_AS:     8576 kB
PageTables:       1344 kB
VmallocTotal: 35184363699328 kB
VmallocUsed:       384 kB
VmallocChunk: 35184363698944 kB

MemTotal:      1006272 kB
MemFree:        670016 kB
Buffers:         14720 kB
Cached:          18304 kB
SwapCached:          0 kB
Active:          35648 kB
Inactive:         9152 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      1006272 kB
LowFree:        670016 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:             256 kB
Writeback:           0 kB
Mapped:           6592 kB
Slab:           212224 kB
Committed_AS:     8576 kB
PageTables:       1344 kB
VmallocTotal: 35184363699328 kB
VmallocUsed:       384 kB
VmallocChunk: 35184363698944 kB

--- [3]

# ./vm.pl; sleep 10; ./vm.pl 
leaked=104640KB
leaked=105664KB
# 102.4kB/s leak rate here

-- 
Daniel J Blueman

NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler!
GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl


             reply	other threads:[~2004-08-06 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-06 14:44 Daniel Blueman [this message]
2004-08-06 14:54 ` [2.6.7, ia64] continual memory leak at ~102kB/s William Lee Irwin III
2004-08-09  9:22   ` Daniel Blueman

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=20029.1091803458@www55.gmx.net \
    --to=daniel.blueman@gmx.net \
    --cc=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --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