From: Michael Raskin <a1d23ab4@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc1-mm1+ memory problem
Date: Sat, 25 Nov 2006 02:07:43 +0300 [thread overview]
Message-ID: <45677B3F.60202@mail.ru> (raw)
In-Reply-To: <4566F26D.2010404@mail.ru>
Michael Raskin wrote:
> Also I have uploaded contents of /proc/page_owner after loosing more
> than 100M. (220M used, 29M - on page_owner, lessthan 50M - for
> processes).
Top 3 entries:
89361 times:
Page allocated via order 0, mask 0x280d2
[0xc0159f31] __handle_mm_fault+1809
[0xc011318a] do_page_fault+314
[0xc04111c4] error_code+116
Can be anything. But if I understand anything, this memory is used
because someone has requested a page that is swapped out. So the memory
must be used, but not reflected in meminfo, and not by a process?
35560 times:
Page allocated via order 0, mask 0x201d2
[0xc0152ec2] __do_page_cache_readahead+450
[0xc015309a] do_page_cache_readahead+74
[0xc014d7b5] filemap_nopage+325
[0xc0159919] __handle_mm_fault+249
[0xc011318a] do_page_fault+314
[0xc04111c4] error_code+116
- is reflected in cache usage statistics, I guess..
6185 times:
Page allocated via order 0, mask 0x200d2
[0xc014e069] generic_file_buffered_write+329
[0xc014e814] __generic_file_aio_write_nolock+612
[0xc014eb85] generic_file_aio_write+85
[0xc01b26ff] ext3_file_write+63
[0xc016b23c] do_sync_write+204
[0xc016b9a7] vfs_write+167
[0xc016c2a7] sys_write+71
[0xc010303a] sysenter_past_esp+95
- negligible, really..
next prev parent reply other threads:[~2006-11-24 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 6:26 2.6.19-rc1-mm1+ memory problem Michael Raskin
2006-11-20 18:18 ` Michael Raskin
2006-11-21 8:37 ` Andrew Morton
[not found] ` <4563485B.3050801@mail.ru>
2006-11-21 19:45 ` Andrew Morton
2006-11-21 21:18 ` Michael Raskin
2006-11-24 13:23 ` Michael Raskin
2006-11-24 23:07 ` Michael Raskin [this message]
2006-11-25 19:03 ` Andrew Morton
2006-11-25 21:53 ` Michael Raskin
2006-11-29 4:29 ` 2.6.19-rc6-mm2 is ok (2.6.19-rc1-mm1+ memory problem) Michael Raskin
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=45677B3F.60202@mail.ru \
--to=a1d23ab4@mail.ru \
--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