public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: kelley eicher <keicher@nws.gov>, J <jack@i2net.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 0-order allocation failed in 2.4.10-pre8
Date: Sun, 16 Sep 2001 10:03:25 +0200	[thread overview]
Message-ID: <20010916100325.B1045@suse.de> (raw)
In-Reply-To: <3BA24EB0.5000402@i2net.com> <Pine.LNX.4.33.0109141342340.14906-100000@home.nohrsc.nws.gov> <20010914210903.E806@suse.de> <20010916015917Z16125-2757+260@humbolt.nl.linux.org>
In-Reply-To: <20010916015917Z16125-2757+260@humbolt.nl.linux.org>

On Sun, Sep 16 2001, Daniel Phillips wrote:
> > Use the
> > 
> > *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.9/block-highmem-all
> > 
> > patch and you can use highmem without having to worry about failed
> > 0-order bounce pages allocations.
> 
> Right, by using 64 bit DMA instead of bounce buffers.  But aren't there cases
> where the 64 bit capable hardware isn't there but somebody still wants to use
> highmem?

Yes of course. The common case is not 64-bit dma here though, it's just
being able to DMA to highmem pages (just full 32-bit dma instead of low
memory dma). And that should cover most systems out there.

-- 
Jens Axboe


  reply	other threads:[~2001-09-16  8:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-14 18:38 0-order allocation failed in 2.4.10-pre8 J
2001-09-14 18:48 ` kelley eicher
2001-09-14 19:09   ` Jens Axboe
2001-09-16  2:06     ` Daniel Phillips
2001-09-16  8:03       ` Jens Axboe [this message]
2001-09-16  9:21         ` Daniel Phillips
2001-09-16  9:24           ` 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=20010916100325.B1045@suse.de \
    --to=axboe@suse.de \
    --cc=jack@i2net.com \
    --cc=keicher@nws.gov \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox