All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [patch] 4GB I/O, cut 5
Date: Thu, 7 Jun 2001 14:41:44 +0200	[thread overview]
Message-ID: <20010607144144.A1522@suse.de> (raw)

Hi,

Changes:

- merge 2.4.6-pre1 zone changes for zone-dma32-6
- correct qlogicfc can_dma_32 flag (Arjan van de Ven)

Arjan also reported that the kernel doesn't boot on a machine with 8GB
of RAM, I'm suspecting the zone-dma32-6 changes. If someone has access
to such a machine, please try it.

There are no bug fixes in this release either - apart from the above
problem, no known bugs exists. I'll be donating a virtual beer for the
first spotted bug.

The patch can be considered stable, it's received quite a bit of testing
on highend hardware. Here's a plug from one such tester:

"Regarding performance of this patch, it is providing us with the highest
aggregate throughput for reads of any of the recent kernels for multiple
IOs - up to 185MB/s continuous through both controllers :)"

*.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.6-pre1/

-- 
Jens Axboe


                 reply	other threads:[~2001-06-07 13:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010607144144.A1522@suse.de \
    --to=axboe@suse.de \
    --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 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.