From: Jens Axboe <axboe@kernel.org>
To: Mark Hemment <markhe@veritas.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
riel@conectiva.com.br, andrea@e-mind.com
Subject: Re: [patch] 4GB I/O, cut three
Date: Wed, 30 May 2001 11:55:38 +0200 [thread overview]
Message-ID: <20010530115538.B15089@suse.de> (raw)
In-Reply-To: <20010529160704.N26871@suse.de> <Pine.LNX.4.21.0105301022410.7153-100000@alloc>
In-Reply-To: <Pine.LNX.4.21.0105301022410.7153-100000@alloc>; from markhe@veritas.com on Wed, May 30, 2001 at 10:43:33AM +0100
On Wed, May 30 2001, Mark Hemment wrote:
> Hi Jens,
>
> I ran this (well, cut-two) on a 4-way box with 4GB of memory and a
> modified qlogic fibre channel driver with 32disks hanging off it, without
> any problems. The test used was SpecFS 2.0
Cool, could you send me the qlogic diff? It's the one-liner can_dma32
chance I'm interested in, I'm just not sure what driver you used :-)
I'll add that to the patch then. Basically all the PCI cards should
work, I'm just being cautious and only enabling highmem I/O to the ones
that have been tested.
> Peformance is definitely up - but I can't give an exact number, as the
> run with this patch was compiled with no-omit-frame-pointer for debugging
> any probs.
Good
> I did change the patch so that bounce-pages always come from the NORMAL
> zone, hence the ZONE_DMA32 zone isn't needed. I avoided the new zone, as
> I'm not 100% sure the VM is capable of keeping the zones it already has
> balanced - and adding another one might break the camels back. But as the
> test box has 4GB, it wasn't bouncing anyway.
You are right, this is definitely something that needs checking. I
really want this to work though. Rik, Andrea? Will the balancing handle
the extra zone?
--
Jens Axboe
next prev parent reply other threads:[~2001-05-30 9:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 14:07 [patch] 4GB I/O, cut three Jens Axboe
2001-05-29 14:11 ` Jens Axboe
2001-05-30 9:43 ` Mark Hemment
2001-05-30 9:55 ` Jens Axboe [this message]
2001-05-30 10:59 ` Mark Hemment
2001-05-30 14:26 ` andrea
2001-05-30 18:42 ` Rik van Riel
2001-05-30 18:57 ` Andrea Arcangeli
2001-05-30 18:57 ` Yoann Vandoorselaere
2001-05-30 19:18 ` Andrea Arcangeli
2001-05-30 19:23 ` Rik van Riel
2001-05-30 14:00 ` Andrea Arcangeli
2001-05-30 14:06 ` Jens Axboe
2001-05-30 18:36 ` Rik van Riel
2001-05-30 13:03 ` Mark Hemment
2001-05-30 13:24 ` Jens Axboe
2001-05-30 13:37 ` Mark Hemment
2001-05-30 13:40 ` 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=20010530115538.B15089@suse.de \
--to=axboe@kernel.org \
--cc=andrea@e-mind.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markhe@veritas.com \
--cc=riel@conectiva.com.br \
/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.