linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* kmemleak issue on ARM target
@ 2010-03-04  9:13 naveen yadav
  2010-03-04 10:18 ` Catalin Marinas
  0 siblings, 1 reply; 2+ messages in thread
From: naveen yadav @ 2010-03-04  9:13 UTC (permalink / raw)
  To: catalin.marinas, linux-kernel, linux-mm

Hi Catalin Marinas ,


W am facing one issue on ARM target, we have 512 MB ram on our target,
we port your patch of
kmemleak(http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-04/msg11830.html)

We are facing problem in DEBUG_KMEMLEAK_EARLY_LOG_SIZE we cannot
increase its size above 1000 because of our kernel Image size for
embedded board
has some limit that if it increase we cannot execute it. so is there
any implementaion possible using vmalloc and not statically allocating
the log of array or else any suggestion.

kind regards
Naveen

--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: kmemleak issue on ARM target
  2010-03-04  9:13 kmemleak issue on ARM target naveen yadav
@ 2010-03-04 10:18 ` Catalin Marinas
  0 siblings, 0 replies; 2+ messages in thread
From: Catalin Marinas @ 2010-03-04 10:18 UTC (permalink / raw)
  To: naveen yadav; +Cc: linux-kernel, linux-mm

On Thu, 2010-03-04 at 09:13 +0000, naveen yadav wrote:
> W am facing one issue on ARM target, we have 512 MB ram on our target,
> we port your patch of
> kmemleak(http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-04/msg11830.html)
> 
> We are facing problem in DEBUG_KMEMLEAK_EARLY_LOG_SIZE we cannot
> increase its size above 1000 because of our kernel Image size for
> embedded board
> has some limit that if it increase we cannot execute it. so is there
> any implementaion possible using vmalloc and not statically allocating
> the log of array or else any suggestion.

Not really. This buffer needs to be static because it is used before
kmemleak is fully initialised. It's also tracking bootmem allocations.

But this size should not increase the Image file size as it should go in
the BSS section.

An additional question - why do you need to increase this size? I found
400 to be enough usually. Do you get any errors?

Since you backported kmemleak, please make sure that you check the
latest code in mm/kmemleak.c as there are some bug-fixes.


-- 
Catalin

--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-03-04 10:18 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-03-04  9:13 kmemleak issue on ARM target naveen yadav
2010-03-04 10:18 ` Catalin Marinas

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).