From: Robert Love <rml@tech9.net>
To: David Brown <dave@codewhore.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Preempt on PowerPC/SMP appears to leak memory
Date: 13 Apr 2003 17:55:27 -0400 [thread overview]
Message-ID: <1050270927.767.4.camel@localhost> (raw)
In-Reply-To: <20030412152951.GA10367@codewhore.org>
On Sat, 2003-04-12 at 11:29, David Brown wrote:
> Before I debug/trace any further, I'm curious as to whether or not
> preempt is known to work on PowerPC in SMP mode. If it's supposed to,
> I'd be happy to capture any data that may help.
It should work OK. The memory leak is certainly unexpected.
Someone else has reported a similar leak on x86... so you are not
alone. It might be a bug in the 2.4.20 kernel itself. Think you can
track down what is leaking?
Robert Love
next prev parent reply other threads:[~2003-04-13 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 15:29 Preempt on PowerPC/SMP appears to leak memory David Brown
2003-04-13 21:55 ` Robert Love [this message]
2003-04-13 21:57 ` Robert Love
2003-04-13 22:02 ` David Brown
2003-04-13 23:03 ` Marc-Christian Petersen
2003-04-13 23:07 ` Robert Love
2003-04-13 23:12 ` Marc-Christian Petersen
2003-04-14 2:26 ` David Brown
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=1050270927.767.4.camel@localhost \
--to=rml@tech9.net \
--cc=dave@codewhore.org \
--cc=linux-kernel@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