From: David Brown <dave@codewhore.org>
To: Robert Love <rml@tech9.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Preempt on PowerPC/SMP appears to leak memory
Date: Sun, 13 Apr 2003 18:02:09 -0400 [thread overview]
Message-ID: <20030413220209.GA5849@codewhore.org> (raw)
In-Reply-To: <1050271044.767.7.camel@localhost>
On Sun, Apr 13, 2003 at 05:57:24PM -0400, Robert Love wrote:
| On Sat, 2003-04-12 at 11:29, David Brown wrote:
|
| > I recently applied the preempt-kernel-rml-2.4.21-pre1-1.patch from
| > kernel.org to BenH's stable tree from rsync.penguinppc.org.
|
| Oh, one other thing. An updated patch for 2.4.20 is up:
|
| http://www.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/preempt-kernel-rml-2.4.20-2.patch
|
| It has a couple fixes for proper protection of per-CPU data, including
| some PPC-specific ones.
|
| Robert Love
Hi Robert:
Thanks for the reply and the patch. I'll give the 2.4.20-2 patch a shot.
If I'm still seeing the leak after applying it, I'll do my best to track
it down (I already know it's somewhere in the fork() path, just based on
the mean-time-before-death of a few test scripts I was playing with).
I probably won't be able to isolate it down to a single line; I should,
however, be able to capture enough information so that someone with far
more awareness of the kernel's guts than I can track it down. :)
Thanks again,
- Dave
next prev parent reply other threads:[~2003-04-13 21:58 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
2003-04-13 21:57 ` Robert Love
2003-04-13 22:02 ` David Brown [this message]
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=20030413220209.GA5849@codewhore.org \
--to=dave@codewhore.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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.