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