From: Colin Gibbs <colin@gibbs.dhs.org>
To: Colin Gibbs <colin@gibbs.dhs.org>
Cc: Tomas Szepe <szepe@pinerecords.com>,
linux-kernel@vger.kernel.org, tcallawa@redhat.com,
sparclinux@vger.kernel.org, aurora-sparc-devel@linuxpower.org
Subject: Re: 2.4 SRMMU bug revisited
Date: 27 May 2002 14:34:05 -0500 [thread overview]
Message-ID: <1022528045.19423.6.camel@monolith> (raw)
In-Reply-To: <1022525198.19147.29.camel@monolith>
On Mon, 2002-05-27 at 13:46, Colin Gibbs wrote:
> What kinds of heavy loads? If you were triggering the out of nocache
> memory BUG, then this patch may help. I fixes a bug where fork fails and
> calls destroy_context on the parent's mm or more precisely a memcpy'd
> duplicate of it. In that case when fork returns to the parent, it
> continuously faults.
>
> But if your load does not fork heavily, then this is probably not the
> problem.
It seems this is in the bitkeeper tree, so ignore that if you used the
bitkeeper tree. However I'd still like to know what sort of loads are
causing you problems.
Colin
next prev parent reply other threads:[~2002-05-27 19:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 9:24 2.4 SRMMU bug revisited Tomas Szepe
2002-05-27 10:17 ` David S. Miller
2002-05-27 6:20 ` Tomas Szepe
2002-05-27 10:40 ` David S. Miller
2002-05-27 11:19 ` [aurora-sparc-devel] " Tomas Szepe
2002-05-28 16:41 ` Denis Vlasenko
2002-05-28 12:11 ` David S. Miller
2002-05-27 18:46 ` Colin Gibbs
2002-05-27 19:34 ` Colin Gibbs [this message]
2002-05-28 1:12 ` Tomas Szepe
2002-05-27 21:30 ` Tomas Szepe
2002-05-28 3:41 ` David S. Miller
2002-05-28 5:40 ` Tomas Szepe
2002-05-28 8:39 ` David Woodhouse
2002-05-28 11:58 ` Alan Cox
2002-05-28 11:05 ` David S. Miller
2002-05-28 12:10 ` Ben Collins
2002-05-28 12:19 ` David S. Miller
2002-05-28 0:40 ` David S. Miller
2002-05-29 21:42 ` Tomas Szepe
[not found] <mailman.1022584088.5530.linux-kernel2news@redhat.com>
2002-05-28 16:12 ` Pete Zaitcev
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=1022528045.19423.6.camel@monolith \
--to=colin@gibbs.dhs.org \
--cc=aurora-sparc-devel@linuxpower.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=szepe@pinerecords.com \
--cc=tcallawa@redhat.com \
/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