public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabio Riccardi <fabio@chromium.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.5-ac1 won't boot with 4GB bigmem option
Date: Sun, 27 May 2001 14:03:40 -0700	[thread overview]
Message-ID: <3B116BAC.F45612F3@chromium.com> (raw)
In-Reply-To: <01052722010200.01106@beastie>

Same here, I have a dual 1GHz PIII with 4G, I don't get an oops but an infinite
loop of:

 > mm: critical shortage of bounce buffers.

Indeed this message has been pestering me in all the recent .4-acx kernels when
the machine is under heavy FS pressure.

In these kernels I observe a significative (5-10%) performance degradation as
soon as the FS cache fills up all the available memory, at this moment "kswapd"
starts to take lots of CPU time (10-20%) and I keep getting plenty of the above
messages.

I'm running SpecWeb with the X15 webserver, which uses sendfile to send its
content, and a very large file set (8-9G, more than twice as much as the
physical RAM).

2.4.2-acx and early 2.4.3-acx kernles were much better in this respect and a lot
more stable.

 - Fabio

Ben Twijnstra wrote:

> Hi,
>
> I compiled and booted the 2.4.5-ac1 kernel with the CONFIG_HIGHMEM4G=y option
> and got an oops in __alloc_pages() (called by alloc_bounce() called by
> schedule()). Everything works fine if I turn the 4GB mode off.
>
> Machine is a Dell Precision with 2 Xeons and 2GB of RAM.
>
> 2.4.5 works fine with the 4GB. Any idea what changed between the two?
>
> Grtz,
>
> Ben
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2001-05-27 20:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-27 20:01 2.4.5-ac1 won't boot with 4GB bigmem option Ben Twijnstra
2001-05-27 21:03 ` Fabio Riccardi [this message]
2001-05-27 21:25   ` Alan Cox
2001-05-27 21:39     ` Fabio Riccardi
2001-05-27 21:21 ` Alan Cox
2001-05-28  7:34   ` Ben Twijnstra

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=3B116BAC.F45612F3@chromium.com \
    --to=fabio@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox