On Sun, May 20, 2012 at 2:01 AM, Marko Zec z...@fer.hr wrote:
Hi all,
I'm playing with an algorithm which makes use of large contiguous blocks of
kernel memory (ranging from 1M to 1G in size), so it would be nice if those
could be somehow forcibly mapped to superpages. I was hoping that the
On Sunday 20 May 2012 09:25:59 Alan Cox wrote:
On Sun, May 20, 2012 at 2:01 AM, Marko Zec z...@fer.hr wrote:
Hi all,
I'm playing with an algorithm which makes use of large contiguous blocks
of kernel memory (ranging from 1M to 1G in size), so it would be nice if
those could be somehow
On 05/20/2012 09:43, Marko Zec wrote:
On Sunday 20 May 2012 09:25:59 Alan Cox wrote:
On Sun, May 20, 2012 at 2:01 AM, Marko Zecz...@fer.hr wrote:
Hi all,
I'm playing with an algorithm which makes use of large contiguous blocks
of kernel memory (ranging from 1M to 1G in size), so it would be
vm.pmap.pde.demotions: 31
No, your conclusion is incorrect. These counts show that 543 superpage
mappings were created by promotion.
OK, that sounds promising. Does created by promotion count reflect
historic / cumulative stats, or is vm.pmap.pde.promotions the actual number
of superpages
On 05/20/2012 17:48, Marko Zec wrote:
On Sunday 20 May 2012 19:34:26 Alan Cox wrote:
...
In any case, I wish to be certain that a particular kmem virtual address
range is mapped to superpages - how can I enforce that at malloc time,
and / or find out later if I really got my kmem mapped to
