From: Andi Kleen <andi@firstfloor.org>
To: "Andrew J. Schorr" <aschorr@telemetry-investments.com>
Cc: linux-numa@vger.kernel.org
Subject: Re: memory leaks in numa_run_on_node
Date: Thu, 27 Jun 2013 02:31:41 +0200 [thread overview]
Message-ID: <20130627003141.GJ6123@two.firstfloor.org> (raw)
In-Reply-To: <20130627000512.GA22273@ti119.telemetry-investments.com>
On Wed, Jun 26, 2013 at 08:05:12PM -0400, Andrew J. Schorr wrote:
> Hi,
>
> According to valgrind, this trivial program has a bunch of memory leaks:
libnuma caches the node masks of CPUs. This is a global cache that
is bounded by the number of CPUs. It's not a leak that will grow
over time.
So it's a false positive.
-Andi
next prev parent reply other threads:[~2013-06-27 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 0:05 memory leaks in numa_run_on_node Andrew J. Schorr
2013-06-27 0:31 ` Andi Kleen [this message]
2013-06-27 0:53 ` Andrew J. Schorr
2013-06-27 1:15 ` Andrew J. Schorr
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=20130627003141.GJ6123@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=aschorr@telemetry-investments.com \
--cc=linux-numa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.