* arm1136 with 2.6.29.5 running out of memory with 32k cache only, 16k and below is fine
@ 2010-07-29 8:14 koen velle
2010-07-29 8:20 ` koen velle
2010-07-29 8:29 ` koen velle
0 siblings, 2 replies; 3+ messages in thread
From: koen velle @ 2010-07-29 8:14 UTC (permalink / raw)
To: linux-arm-msm
Hi,
I've got a (simulated) system where I can select my cache sizes. Boot
goes fine with 4, 8, and 16k cache, but goes boink with 32k cache.
While debugging, I'm able to find out that in __do_page_fault, I end
up at the label out_of_memory, as handle_mm_fault returns
VM_FAULT_OOM.
This does not happen with caches <32k. Otherwise, both my system and
my linux config are identical, only the cache size is different.
Is there anything that can explain this ? Do I need to modify the
kernel configuration somehow if I want to use 32k caches ? Does the
kernel consume more memory when using 32k caches due to dealing with
cache coloring ?
In short, any easy answers ?
Thanks,
Koen.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: arm1136 with 2.6.29.5 running out of memory with 32k cache only, 16k and below is fine
2010-07-29 8:14 arm1136 with 2.6.29.5 running out of memory with 32k cache only, 16k and below is fine koen velle
@ 2010-07-29 8:20 ` koen velle
2010-07-29 8:29 ` koen velle
1 sibling, 0 replies; 3+ messages in thread
From: koen velle @ 2010-07-29 8:20 UTC (permalink / raw)
To: linux-arm-msm
That should read ARM1176, not ARM1136, sorry for that... (but probably
does not make much difference)
Koen.
On Thu, Jul 29, 2010 at 10:14 AM, koen velle <koen.velle@gmail.com> wrote:
> Hi,
>
> I've got a (simulated) system where I can select my cache sizes. Boot
> goes fine with 4, 8, and 16k cache, but goes boink with 32k cache.
> While debugging, I'm able to find out that in __do_page_fault, I end
> up at the label out_of_memory, as handle_mm_fault returns
> VM_FAULT_OOM.
>
> This does not happen with caches <32k. Otherwise, both my system and
> my linux config are identical, only the cache size is different.
>
> Is there anything that can explain this ? Do I need to modify the
> kernel configuration somehow if I want to use 32k caches ? Does the
> kernel consume more memory when using 32k caches due to dealing with
> cache coloring ?
>
> In short, any easy answers ?
>
> Thanks,
>
> Koen.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: arm1136 with 2.6.29.5 running out of memory with 32k cache only, 16k and below is fine
2010-07-29 8:14 arm1136 with 2.6.29.5 running out of memory with 32k cache only, 16k and below is fine koen velle
2010-07-29 8:20 ` koen velle
@ 2010-07-29 8:29 ` koen velle
1 sibling, 0 replies; 3+ messages in thread
From: koen velle @ 2010-07-29 8:29 UTC (permalink / raw)
To: linux-arm-msm
Dear all,
sorry for posting this to the wrong list, should have gone to
linux-arm-kernel, please ignore.
Koen.
On Thu, Jul 29, 2010 at 10:14 AM, koen velle <koen.velle@gmail.com> wrote:
> Hi,
>
> I've got a (simulated) system where I can select my cache sizes. Boot
> goes fine with 4, 8, and 16k cache, but goes boink with 32k cache.
> While debugging, I'm able to find out that in __do_page_fault, I end
> up at the label out_of_memory, as handle_mm_fault returns
> VM_FAULT_OOM.
>
> This does not happen with caches <32k. Otherwise, both my system and
> my linux config are identical, only the cache size is different.
>
> Is there anything that can explain this ? Do I need to modify the
> kernel configuration somehow if I want to use 32k caches ? Does the
> kernel consume more memory when using 32k caches due to dealing with
> cache coloring ?
>
> In short, any easy answers ?
>
> Thanks,
>
> Koen.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-07-29 8:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-07-29 8:14 arm1136 with 2.6.29.5 running out of memory with 32k cache only, 16k and below is fine koen velle
2010-07-29 8:20 ` koen velle
2010-07-29 8:29 ` koen velle
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).