From: Phil Carmody <ext-phil.2.carmody@nokia.com>
To: "Doyu Hiroshi (Nokia-D/Helsinki)" <hiroshi.doyu@nokia.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC][PATCH 0/1] kmemleak: Fix false positive with alias
Date: Tue, 22 Jun 2010 18:36:33 +0300 [thread overview]
Message-ID: <20100622153633.GY17639@pcarmody-desktop> (raw)
In-Reply-To: <1276841055-13843-1-git-send-email-Hiroshi.DOYU@nokia.com>
On 18/06/10 08:04 +0200, Doyu Hiroshi (Nokia-D/Helsinki) wrote:
> Hi,
>
> This is another version of "kmemleak: Fix false positive", which
> introduces another alias tree to keep track of all alias address of
> each objects, based on the discussion(*1)
>
> You can also find the previous one(*2), which uses special scan area
> for alias addresses with a conversion function.
>
> Compared with both methods, it seems that the current one takes a bit
> longer to scan as below, tested with 512 elementes of (*3).
>
> "kmemleak: Fix false positive with alias":
> # time echo scan > /mnt/kmemleak
> real 0m 8.40s
> user 0m 0.00s
> sys 0m 8.40s
>
> "kmemleak: Fix false positive with special scan":
> # time echo scan > /mnt/kmemleak
> real 0m 3.96s
> user 0m 0.00s
> sys 0m 3.96s
>
> For our case(*4) to reduce false positives for the 2nd level IOMMU
> pagetable allocation, the previous special scan seems to be enough
> lightweight, although there might be possiblity to improve alias
> one and also I might misunderstand the original proposal of aliasing.
>
> Any comment would be appreciated.
After comparing the two, my Ack would still strongly be behind the
first one, the special scan. The additional work over a normal scan
is limited strictly to those regions that need it, which is a much
more clinical approach to the problem. Your timing data bears that
out.
Phil
> *1: http://lkml.org/lkml/2010/6/2/282
> *2: kmemleak: Fix false positive with special scan
> http://lkml.org/lkml/2010/6/1/137
> *3: kmemleak: Add special scan test case
> http://lkml.org/lkml/2010/6/1/134
> *4: http://lkml.org/lkml/2010/6/1/136
>
> Hiroshi DOYU (1):
> kmemleak: Fix false positive with alias
>
> include/linux/kmemleak.h | 4 +
> mm/kmemleak.c | 198 ++++++++++++++++++++++++++++++++++++++--------
> 2 files changed, 168 insertions(+), 34 deletions(-)
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-22 15:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1273821401-26578-2-git-send-email-Hiroshi.DOYU@nokia.com>
2010-06-01 10:25 ` [PATCH v2 0/3] kmemleak: Fix false positive with special scan Hiroshi DOYU
2010-06-02 10:01 ` Catalin Marinas
2010-06-02 11:34 ` Hiroshi DOYU
2010-06-02 12:28 ` Hiroshi DOYU
2010-06-02 14:12 ` Catalin Marinas
2010-06-03 9:54 ` Hiroshi DOYU
2010-06-18 6:04 ` [RFC][PATCH 0/1] kmemleak: Fix false positive with alias Hiroshi DOYU
2010-06-22 15:36 ` Phil Carmody [this message]
2010-06-28 14:46 ` Catalin Marinas
2010-06-29 4:44 ` Hiroshi DOYU
2010-08-10 15:49 ` Hiroshi DOYU
2010-08-27 6:12 ` Hiroshi DOYU
2010-08-30 20:30 ` Paul E. McKenney
2010-09-17 13:14 ` Catalin Marinas
2010-09-17 16:18 ` Catalin Marinas
2010-09-17 17:06 ` Hiroshi DOYU
2010-09-17 17:28 ` Phil Carmody
2010-06-18 6:04 ` [PATCH 1/1] " Hiroshi DOYU
2010-06-01 10:25 ` [PATCH v2 1/3] kmemleak: Fix false positives with special scan Hiroshi DOYU
2010-06-01 10:25 ` [PATCH v2 2/3] kmemleak: Add special scan test case Hiroshi DOYU
2010-06-01 10:25 ` [PATCH v2 3/3] omap iommu: kmemleak: Fix false positive with special scan Hiroshi DOYU
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=20100622153633.GY17639@pcarmody-desktop \
--to=ext-phil.2.carmody@nokia.com \
--cc=catalin.marinas@arm.com \
--cc=hiroshi.doyu@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.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