All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Sweeney <v.sweeney@dexterus.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: More 2.4 memory usage wierdness?
Date: Thu, 22 Mar 2001 12:19:47 +0000	[thread overview]
Message-ID: <3AB9EDE3.E01A2AA8@dexterus.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 733 bytes --]

I have a question regarding a busy box I recently updated to
'2.4.2-ac20'. It has been running for several hours without any real
problems until I started getting 'dmesg' entries like:

Out of Memory: Killed process 30293 (httpd).
Out of Memory: Killed process 32552 (mysqld).

Not a quick check with 'top' shows:

Mem:   771440K av,  396060K used,  375380K free,       0K shrd,    4972K
buff
Swap:  379416K av,  345000K used,   34416K free                  337128K
cached

I have also attached my "/proc/meminfo" & "/proc/slabinfo" details.

Basically they all show the server has 370MB of free physical memory but
its using lots of swap space and OOM is killing processes.

What gives?

Vince.

-- 
Vincent Sweeney
System Architect

[-- Attachment #2: meminfo --]
[-- Type: application/octet-stream, Size: 549 bytes --]

        total:    used:    free:  shared: buffers:  cached:
Mem:  789954560 405225472 384729088        0  5054464 344883200
Swap: 388521984 353280000 35241984
MemTotal:       771440 kB
MemFree:        375712 kB
MemShared:           0 kB
Buffers:          4936 kB
Cached:         336800 kB
Active:          92700 kB
Inact_dirty:    247312 kB
Inact_clean:      1724 kB
Inact_target:      112 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       771440 kB
LowFree:        375712 kB
SwapTotal:      379416 kB
SwapFree:        34416 kB

[-- Attachment #3: slabinfo --]
[-- Type: application/octet-stream, Size: 3726 bytes --]

slabinfo - version: 1.1 (SMP)
kmem_cache            68     68    232    4    4    1 :  252  126
ip_conntrack         692    867    224   50   51    1 :  252  126
tcp_tw_bucket        375    400     96   10   10    1 :  252  126
tcp_bind_bucket      276    339     32    3    3    1 :  252  126
tcp_open_request     295    295     64    5    5    1 :  252  126
inet_peer_cache        0      0     64    0    0    1 :  252  126
ip_fib_hash           17    226     32    2    2    1 :  252  126
ip_dst_cache         521    648    160   26   27    1 :  252  126
arp_cache              5     60    128    2    2    1 :  252  126
blkdev_requests     4608   4640     96  116  116    1 :  252  126
dnotify cache          0      0     20    0    0    1 :  252  126
file lock cache      126    126     92    3    3    1 :  252  126
fasync cache           0      0     16    0    0    1 :  252  126
uid_cache            226    226     32    2    2    1 :  252  126
skbuff_head_cache   1003   1272    160   51   53    1 :  252  126
sock                 340    340    800   68   68    1 :  124   62
inode_cache         2576   2576    480  322  322    1 :  124   62
bdev_cache             6    177     64    2    3    1 :  252  126
sigqueue             116    116    132    4    4    1 :  252  126
kiobuf                 0      0    128    0    0    1 :  252  126
dentry_cache        3216   3570    128  119  119    1 :  252  126
dquot                  0      0    128    0    0    1 :  252  126
filp                 954   1000     96   25   25    1 :  252  126
names_cache           23     23   4096   23   23    1 :   60   30
buffer_head        15000  15000     96  375  375    1 :  252  126
mm_struct            300    336    160   13   14    1 :  252  126
vm_area_struct      7990  10384     64  150  176    1 :  252  126
fs_cache             321    354     64    6    6    1 :  252  126
files_cache          225    225    416   25   25    1 :  124   62
signal_act           162    162   1312   54   54    1 :   60   30
size-131072(DMA)       0      0 131072    0    0   32 :    0    0
size-131072            0      0 131072    0    0   32 :    0    0
size-65536(DMA)        0      0  65536    0    0   16 :    0    0
size-65536             1      1  65536    1    1   16 :    0    0
size-32768(DMA)        0      0  32768    0    0    8 :    0    0
size-32768             4     10  32768    4   10    8 :    0    0
size-16384(DMA)        0      0  16384    0    0    4 :    0    0
size-16384             0      1  16384    0    1    4 :    0    0
size-8192(DMA)         0      0   8192    0    0    2 :    0    0
size-8192              0     15   8192    0   15    2 :    0    0
size-4096(DMA)         0      0   4096    0    0    1 :   60   30
size-4096             92     92   4096   92   92    1 :   60   30
size-2048(DMA)         0      0   2048    0    0    1 :   60   30
size-2048            348    378   2048  174  189    1 :   60   30
size-1024(DMA)         0      0   1024    0    0    1 :  124   62
size-1024            254    316   1024   68   79    1 :  124   62
size-512(DMA)          0      0    512    0    0    1 :  124   62
size-512             120    120    512   15   15    1 :  124   62
size-256(DMA)          0      0    256    0    0    1 :  252  126
size-256             285    285    256   19   19    1 :  252  126
size-128(DMA)          0      0    128    0    0    1 :  252  126
size-128            1020   1020    128   34   34    1 :  252  126
size-64(DMA)           0      0     64    0    0    1 :  252  126
size-64              427    767     64   13   13    1 :  252  126
size-32(DMA)           0      0     32    0    0    1 :  252  126
size-32              824   6215     32   53   55    1 :  252  126

             reply	other threads:[~2001-03-22 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 12:19 Vincent Sweeney [this message]
2001-03-22 16:50 ` More 2.4 memory usage wierdness? Vincent Sweeney

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=3AB9EDE3.E01A2AA8@dexterus.com \
    --to=v.sweeney@dexterus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.