From: Markus Lidel <Markus.Lidel@shadowconnect.com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH 2.6] partly rewritten I2O subsystem to better fit into 2.6 kernel
Date: Fri, 23 Jul 2004 00:40:55 +0200 [thread overview]
Message-ID: <41004277.1010106@shadowconnect.com> (raw)
Hello,
finally there is a new version of the I2O subsystem available. The patch
is 600k large and available under:
http://i2o.shadowconnect.com/patches/i2o-build_92.patch
and also bzip2 compressed under:
http://i2o.shadowconnect.com/patches/i2o-build_92.patch.bz2
The major benefits are:
- sysfs support
- PCI probing (which now should allow PCI hotplugging)
- dynamically allocated request queues and gendisks for block devices
and a own request queue per disk (which results in much better
performance on many parallel requests)
To verify the stability, we've run 4 parallel bonnie++ on a dual Opteron
on 4 separate disks without a problem. To generate huge load we've also
created a ext2 filesystem on all 4 disks in parallel. This lead to
hangups of single disks in earlier versions, but is now fixed.
Also the driver was tested on 32-bit as well, but only with 2 disks :-)
Compared to my last post, all subsystems are now converted to use the
new API.
Please include the patch to get a wider exposure to test it, and let me
know, if there is something missing or there is something to change.
Any comment is appreciated.
Best regards,
Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)
Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany
Phone: +49 82 82/99 51-0
Fax: +49 82 82/99 51-11
E-Mail: Markus.Lidel@shadowconnect.com
URL: http://www.shadowconnect.com
reply other threads:[~2004-07-22 22:49 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=41004277.1010106@shadowconnect.com \
--to=markus.lidel@shadowconnect.com \
--cc=linux-scsi@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.