From: Christoph Hellwig <hch@ns.caldera.de>
To: Peter Wong <wpeter@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] Regarding Jens' Zero-Bounce Highmem I/O Patch
Date: Thu, 20 Sep 2001 00:10:48 +0200 [thread overview]
Message-ID: <20010920001048.A11073@caldera.de> (raw)
In-Reply-To: <OF2D7B8881.082D3FA6-ON85256ACC.0075C7C8@raleigh.ibm.com>
In-Reply-To: <OF2D7B8881.082D3FA6-ON85256ACC.0075C7C8@raleigh.ibm.com>; from wpeter@us.ibm.com on Wed, Sep 19, 2001 at 05:04:59PM -0500
On Wed, Sep 19, 2001 at 05:04:59PM -0500, Peter Wong wrote:
> In order to use Jens' zero-bounce highmem I/O patch against 2.4.6,
> a small modification for the patch is needed. Simply replace
> GFP_BUFFER by GFP_NOIO in block-highmem-all-5.gz, which can be obtained
> at http://www.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.6-pre1/.
>
> However, there is another problem. For both 2.4.5 and 2.4.6 with
> Jens' patches, if the kernels are built with 4GB highmem, they
> boot without problems. But if the kernels are built with 64GB
> highmem, the kernels hang right after uncompressing Linux. Has
> anyone seen this problem?
block-highmem-all-5 is _very_ _very_ old.
Please upgrade to a recent kernel and patch and report again.
I had a system with PAE enabled and 2.4.9ac + some hacked block-highmem
patch running very well here. (Probably it still runns :))
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-09-19 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 22:04 Regarding Jens' Zero-Bounce Highmem I/O Patch Peter Wong
2001-09-19 22:10 ` Christoph Hellwig [this message]
2001-09-23 10:47 ` Jens Axboe
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=20010920001048.A11073@caldera.de \
--to=hch@ns.caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=wpeter@us.ibm.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 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.