All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Per Andreas Buer <perbu@linpro.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4: mylex and > 2GB RAM
Date: Mon, 8 Dec 2003 13:36:39 -0800	[thread overview]
Message-ID: <20031208213639.GB19856@holomorphy.com> (raw)
In-Reply-To: <1070918737.1260.62.camel@localhost.localdomain>

On Mon, 2003-12-08 at 22:02, William Lee Irwin III wrote:
>> Actually, this suggests lowmem starvation due to bounce buffering.

On Mon, Dec 08, 2003 at 10:25:37PM +0100, Per Andreas Buer wrote:
> The kernel is compiled with CONFIG_HIGHIO=y. Do you know if this is a
> DAC960 issue or a chipset issue?

It uses blk_init_queue() and so gets default bouncing behavior of
bouncing everything not in kernel virtualspace; blk_queue_bounce_limit()
would describe the device's actual limits to the system. I don't know
what they are offhand, though, so I can't tell you what to try.


-- wli

  reply	other threads:[~2003-12-08 21:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 15:24 2.4: mylex and > 2GB RAM Per Buer
2003-12-08 15:36 ` William Lee Irwin III
2003-12-08 15:54   ` Per Buer
2003-12-08 16:22     ` William Lee Irwin III
2003-12-08 20:15       ` Per Andreas Buer
2003-12-08 20:22         ` William Lee Irwin III
2003-12-08 21:01           ` Per Andreas Buer
2003-12-08 21:02             ` William Lee Irwin III
2003-12-08 21:25               ` Per Andreas Buer
2003-12-08 21:36                 ` William Lee Irwin III [this message]
2003-12-09 10:31             ` Marcelo Tosatti
2003-12-10 13:21               ` Per Buer
2003-12-08 20:40         ` Zwane Mwaikambo
  -- strict thread matches above, loose matches on Subject: below --
2003-12-08 15:58 Hank Leininger

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=20031208213639.GB19856@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perbu@linpro.no \
    /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.