From: Andrea Arcangeli <andrea@suse.de>
To: Marvin Justice <Mjustice@boxxtech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.13-pre5-aa1 O_DIRECT drastic HIGHMEM performance hit
Date: Fri, 26 Oct 2001 13:48:19 +0200 [thread overview]
Message-ID: <20011026134819.D30905@athlon.random> (raw)
In-Reply-To: <3B6867E6CB09B24385A73719A50C7C9A01797E@athena.boxxtech.com>
In-Reply-To: <3B6867E6CB09B24385A73719A50C7C9A01797E@athena.boxxtech.com>; from Mjustice@boxxtech.com on Thu, Oct 25, 2001 at 11:57:08AM -0500
On Thu, Oct 25, 2001 at 11:57:08AM -0500, Marvin Justice wrote:
> Are we stuck with a low mem configuration or are there workarounds that
> would allow us to stick with the initial 2GB of RAM and still get ~200
> MB/sec.
the problem you seen isn't specific to O_DIRECT. This should solve your
problem (not just for O_DIRECT):
ftp://ftp.us.kernel.org/pub/linux/kernel/people/people/axboe/patches/2.4.13-pre4/block-highmem-all-17.bz2
It's a long time that I want to include the anti-bounce bits, but I am
still looking into the vm. The uglier part is that I suspect we'll also
need to make a 2G bounce option for some hardware combination. I hope
I'm wrong :).
Andrea
prev parent reply other threads:[~2001-10-26 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 16:57 2.4.13-pre5-aa1 O_DIRECT drastic HIGHMEM performance hit Marvin Justice
2001-10-25 17:20 ` Alan Cox
2001-10-26 11:48 ` Andrea Arcangeli [this message]
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=20011026134819.D30905@athlon.random \
--to=andrea@suse.de \
--cc=Mjustice@boxxtech.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