From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Panic on 2.6.0-test1-mm1
Date: Thu, 31 Jul 2003 18:02:16 -0700 [thread overview]
Message-ID: <20030801010216.GN15452@holomorphy.com> (raw)
In-Reply-To: <393910000.1059699469@flay>
At some point in the past, I wrote:
>> pgd_dtor() will never be called on PAE due to the above code (thanks to
>> the PTRS_PER_PMD check), _unless_ mingo's patch is applied (which backs
>> out the PTRS_PER_PMD check).
On Thu, Jul 31, 2003 at 05:57:49PM -0700, Martin J. Bligh wrote:
> OK, might have made a mistake ... I can rerun it if you want, but the
> latest kernel seems to work now.
There was a spinlock acquisition in there, too, so if you're seeing
weird performance effects in an update (not sure if there are any yet),
generating a patch to skip that, the list op, and not install pgd_dtor()
when PTRS_PER_PMD == 1 is in order.
-- wli
prev parent reply other threads:[~2003-08-01 1:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 14:37 Panic on 2.6.0-test1-mm1 Martin J. Bligh
2003-07-29 21:18 ` Martin J. Bligh
2003-07-30 15:01 ` 2.6.0-test2-mm1 results Martin J. Bligh
2003-07-30 15:28 ` Con Kolivas
2003-07-30 16:27 ` Martin J. Bligh
2003-07-31 14:56 ` Martin J. Bligh
2003-07-31 15:13 ` Con Kolivas
2003-07-31 15:19 ` Martin J. Bligh
2003-07-31 15:35 ` Con Kolivas
2003-07-31 16:01 ` Martin J. Bligh
2003-07-31 16:11 ` Con Kolivas
2003-07-31 21:19 ` William Lee Irwin III
2003-07-31 17:03 ` Bill Davidsen
2003-07-31 22:37 ` Panic on 2.6.0-test1-mm1 William Lee Irwin III
2003-07-31 22:41 ` William Lee Irwin III
2003-07-31 22:40 ` Andrew Morton
2003-08-01 0:15 ` William Lee Irwin III
2003-08-01 0:18 ` Zwane Mwaikambo
2003-08-01 0:20 ` William Lee Irwin III
2003-08-01 0:47 ` Martin J. Bligh
2003-08-01 0:53 ` William Lee Irwin III
2003-08-01 0:57 ` Martin J. Bligh
2003-08-01 1:02 ` William Lee Irwin III [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=20030801010216.GN15452@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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;
as well as URLs for NNTP newsgroup(s).