From: Christoph Rohland <cr@sap.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] VM kswapd autotuning vs. -ac7
Date: 05 Jun 2000 10:58:48 +0200 [thread overview]
Message-ID: <qwwvgzov707.fsf@sap.com> (raw)
In-Reply-To: qww7lc5wvhx.fsf@sap.com
Christoph Rohland <cr@sap.com> writes:
> From a short view #3 looks much better, but one thing is disturbing me:
>
> 12 0 0 0 492440 1604 10200 0 0 0 0 104 72356 5 94 1
> shmget: Cannot allocate memory
> 9 2 1 8992 610136 148 13840 0 1798 3 452 1581 83181 0 90 9
>
> it begins swapping with 490MB free and fails to allocate a shm segment?
O.k. more (not that nice) data from the same run:
3 9 1 235720 2404 96 12576 58 18585 21 4648 13905 35860 0 85
15
VM: killing process ipctst
4 6 1 11004 113588 100 19804 78 39615 20 9904 2542 27828 0 16 83
VM: killing process ipctst
VM: killing process ipctst
shmget: Cannot allocate memory
VM: killing process ipctst
3 3 1 109996 3176 96 13884 239 20720 63 5180 1312 132803 1 38
61
VM: killing process ipctst
0 5 1 264652 2012 96 13544 2 30912 0 7728 1636 11053 0 10 90
[...] Killing until only one ipctst is running and then a long time no swap
1 0 0 282760 606512 116 11360 0 0 0 0 107 1272 1 11 87
1 0 0 282760 656164 116 11360 0 0 0 0 103 2 1 12 87
1 0 0 282760 4664 116 11360 0 0 0 0 105 2 1 12 87
4294967295 1 1 323808 2032 96 12828 1 8226 0 2057 533 1600 1 7 92
VM: killing process vmstat
VM: killing process bash
VM: killing process init
NMI Watchdog detected LOCKUP on CPU6, registers: CPU: 6
EIP: 0010:[<c011efed>]
EFLAGS: 00000002
eax: c1088000 ebx: f7400000 ecx: c02c20a4 edx: c02c20a4
esi: 00000368 edi: c1088000 ebp: c1088000 esp: c1089eec
ds: 0018 es: 0018 ss: 0018
Process init (pid: 1, stackpage=c1089000)
Stack: c1088000 c0289c60 00000009 08050054 c011f362 00000004 c3fce05c c1088000
c0114304 00000009 c1088000 0804ff80 40105720 bffff68c c3fcc200 c3fce078
c3fce078 c3fce05c c3fce040 bffffa50 bffff9d0 00030002 ffffffff c1089fa4
Call Trace: [<c011f362>] [<c0114304>] [<c010b125>]
Call Trace: [<c011f362>] [<c0114304>] [<c010b125>]
Code: 89 83 80 00 00 00 8b 80 84 00 00 00 89 83 8c 00 00 00 85 c0
>>EIP; c011efed <exit_notify+165/270> <=====
Trace; c011f362 <do_exit+26a/2ac>
Trace; c0114304 <do_page_fault+4b4/570>
Trace; c010b125 <error_code+2d/38>
Code: 89 83 80 00 00 00 8b 80 84 00 00 00 89 83 8c 00 00 00 85 c0
Code; c011efed <exit_notify+165/270>
00000000 <_EIP>:
Code; c011efed <exit_notify+165/270> <=====
0: 89 83 80 00 00 00 movl %eax,0x80(%ebx) <=====
Code; c011eff3 <exit_notify+16b/270>
6: 8b 80 84 00 00 00 movl 0x84(%eax),%eax
Code; c011eff9 <exit_notify+171/270>
c: 89 83 8c 00 00 00 movl %eax,0x8c(%ebx)
Code; c011efff <exit_notify+177/270>
12: 85 c0 testl %eax,%eax
console shuts up ...
Please note the ridiculous vmstat output before/while going
berserk. (But at least the kernel now notifies again when killing
processes)
Greetings
Christoph
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-06-05 8:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-01 22:31 [PATCH] VM kswapd autotuning vs. -ac7 Rik van Riel
2000-06-02 15:54 ` Christoph Rohland
2000-06-02 16:01 ` Rik van Riel
2000-06-03 9:02 ` Christoph Rohland
2000-06-03 20:47 ` Rik van Riel
2000-06-04 11:12 ` Christoph Rohland
2000-06-05 8:58 ` Christoph Rohland [this message]
2000-06-05 10:16 ` Rik van Riel
2000-06-07 10:23 ` Christoph Rohland
2000-06-07 12:43 ` Rik van Riel
2000-06-07 13:04 ` Christoph Rohland
2000-06-07 13:39 ` Rik van Riel
2000-06-07 14:29 ` Christoph Rohland
2000-06-07 14:43 ` Stephen C. Tweedie
2000-06-08 15:04 ` [PATCH,incomplete] shm integration into shrink_mmap Christoph Rohland
2000-06-08 15:21 ` Juan J. Quintela
2000-06-08 15:35 ` Rik van Riel
2000-06-07 13:32 ` [PATCH] VM kswapd autotuning vs. -ac7 Stephen C. Tweedie
2000-06-07 14:09 ` Jamie Lokier
2000-06-07 14:11 ` Christoph Rohland
2000-06-07 14:17 ` Stephen C. Tweedie
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=qwwvgzov707.fsf@sap.com \
--to=cr@sap.com \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
/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.