From: Catalin Marinas <catalin.marinas@arm.com>
To: naveen yadav <yad.naveen@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: kmemleak issue on ARM target
Date: Thu, 04 Mar 2010 10:18:44 +0000 [thread overview]
Message-ID: <1267697924.6526.5.camel@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <9bde694e1003040113k3b573957h1b831c8d25205d22@mail.gmail.com>
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>
prev parent reply other threads:[~2010-03-04 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 9:13 kmemleak issue on ARM target naveen yadav
2010-03-04 10:18 ` Catalin Marinas [this message]
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=1267697924.6526.5.camel@e102109-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yad.naveen@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).