From: Arjan van de Ven <arjanv@redhat.com>
To: "Philip R. Auld" <pauld@egenera.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [dm-devel] Re: Is there a grand plan for FC failover?
Date: Thu, 12 Feb 2004 16:28:41 +0100 [thread overview]
Message-ID: <1076599721.4442.4.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20040212101705.F27680@vienna.EGENERA.COM>
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
> That size is based on the blocksize? Is there a way to set the block size higher than
> 512 w/o mounting it? I've gotten really bad rawio performance on 2.4. since I have a
> limit of 32 sg entries. When Rawio uses a 512 byte blocksize IOs are limited to 16K.
>
> Will this still be a problem in 2.6?
If you code the driver right, it's not even a problem in 2.4 if you use
a Enterprise Linux distro kernel.....
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-12 15:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 14:18 Is there a grand plan for FC failover? Simon Kelley
2004-01-26 15:37 ` James Bottomley
2004-01-28 15:02 ` Philip R. Auld
2004-01-28 16:57 ` James Bottomley
2004-01-28 18:00 ` Philip R. Auld
2004-01-28 20:47 ` Patrick Mansfield
2004-01-28 22:14 ` James Bottomley
2004-01-29 0:55 ` Patrick Mansfield
2004-01-30 19:48 ` [dm-devel] " Joe Thornber
2004-01-31 9:30 ` Jens Axboe
2004-01-31 16:59 ` Philip R. Auld
2004-01-31 17:42 ` Jens Axboe
2004-02-12 15:17 ` Philip R. Auld
2004-02-12 15:28 ` Arjan van de Ven [this message]
2004-02-12 16:03 ` Philip R. Auld
2004-01-28 22:37 ` Mike Christie
2004-01-29 15:24 ` Philip R. Auld
2004-01-29 16:00 ` James Bottomley
2004-01-29 23:25 ` Mike Christie
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=1076599721.4442.4.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=pauld@egenera.com \
/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