From: William Lee Irwin III <wli@holomorphy.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Chuck Luciano <chuck@mrluciano.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: redhat 2.4.20 kernel 3.5G patch, bug report on my previous 2.4.18 kernel 3.5G patch
Date: Tue, 19 Aug 2003 14:39:37 -0700 [thread overview]
Message-ID: <20030819213937.GA4306@holomorphy.com> (raw)
In-Reply-To: <1061327818.25944.48.camel@nighthawk>
On Tue, Aug 19, 2003 at 02:16:58PM -0700, Dave Hansen wrote:
> Actually, I would just do what we did in 2.5 and throw away *_pgd_fast()
> functions and just use a slab constructor and destructor to handle it
> for you.
Please be patient for the preconstruction that works with highpte; I
have code, but am holding back to keep the number of potentially
destabilizing changes simultaneously in the air down to a reasonable
number.
-- wli
next prev parent reply other threads:[~2003-08-19 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 17:55 redhat 2.4.20 kernel 3.5G patch, bug report on my previous 2.4.18 kernel 3.5G patch Chuck Luciano
2003-08-19 21:16 ` Dave Hansen
2003-08-19 21:39 ` William Lee Irwin III [this message]
2003-08-19 22:51 ` redhat 2.4.20 kernel 3.5G patch, bug report on my previous2.4.18 " Chuck Luciano
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=20030819213937.GA4306@holomorphy.com \
--to=wli@holomorphy.com \
--cc=chuck@mrluciano.com \
--cc=haveblue@us.ibm.com \
--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 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.