From: Jens Axboe <jens.axboe@oracle.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [BTT PATCH] Fix memory leak
Date: Fri, 13 Apr 2007 18:14:49 +0000 [thread overview]
Message-ID: <20070413181449.GJ19066@kernel.dk> (raw)
In-Reply-To: <4617D567.500@pobox.com>
On Sat, Apr 07 2007, Alan D. Brunelle wrote:
> [[Note: I do not have access to my work mail right now, so I'm doing
> this quite blind - please excuse me if I've got the name wrong below...]]
>
> Hi Jens -
>
> A couple of weeks ago Ming Zhang had noted that btt was using tremendous
> amounts of memory to accomplish a run. After looking at the code, and
> doing some testing, I determined the cause - please find a patch to the
> latest tree that seems to fix the problem for me...
Alan,
I applied this one and tried to apply the rest of your posted patches,
but some of them fail. So I stopped after this one, can you resend the
series against the current HEAD? Thanks!
--
Jens Axboe
prev parent reply other threads:[~2007-04-13 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-07 17:31 [BTT PATCH] Fix memory leak Alan D. Brunelle
2007-04-08 18:10 ` Ming Zhang
2007-04-13 18:14 ` Jens Axboe [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=20070413181449.GJ19066@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-btrace@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;
as well as URLs for NNTP newsgroup(s).