mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steffen Persvold <sp@scali.no>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: mm: critical shortage of bounce buffers
Date: Fri, 28 Sep 2001 21:39:46 +0200	[thread overview]
Message-ID: <3BB4D202.314C98E6@scali.no> (raw)
In-Reply-To: <E15n2Rf-0007xv-00@the-village.bc.nu> <3BB4D072.4D3EE56B@scali.no>

Steffen Persvold wrote:
> 
> Alan Cox wrote:
> >
> > > I've recently encountered the following message on a machine running RedHat's
> > > 2.4.3-12 kernel :
> > >
> > > "mm: critical shortage of bounce buffers"
> > >
> > > I've searched through the kernel sources, but my 'find' just can't locate this
> > > string anywhere.
> >
> > Its in the high mem handling routines. It means the machine stalled for
> > a moment doing I/O because it had no memory below 1Gb to use.
> 
> But why does it need to have memory below 1Gb ?? Normally, 32bit PCI DMA
> controllers (such as network cards and disk controllers) can access up to 4GB of
> physical memory within the machine, so unless you are using the CONFIG_HIGHMEM4G
> option it shouldn't need bounce buffers.

Sorry  that should have been the CONFIG_HIGHMEM64G option. I think the
CONFIG_HIGHMEM4G option could manage without bounce buffers.

Regards,
-- 
  Steffen Persvold   | Scalable Linux Systems |   Try out the world's best   
 mailto:sp@scali.no  |  http://www.scali.com  | performing MPI implementation:
Tel: (+47) 2262 8950 |   Olaf Helsets vei 6   |      - ScaMPI 1.12.2 -         
Fax: (+47) 2262 8951 |   N0621 Oslo, NORWAY   | >300MBytes/s and <4uS latency

  reply	other threads:[~2001-09-28 19:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-28 18:19 Steffen Persvold
2001-09-28 18:33 ` Alan Cox
2001-09-28 19:33   ` Steffen Persvold
2001-09-28 19:39     ` Steffen Persvold [this message]
2001-09-28 22:16     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-05-08  2:39 Sergey Kubushin

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=3BB4D202.314C98E6@scali.no \
    --to=sp@scali.no \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®