From: Jens Axboe <axboe@suse.de>
To: Matt_Domsch@Dell.com
Cc: jason@heymax.com, linux-kernel@vger.kernel.org, gandalf@winds.org
Subject: Re: aacraid 2.4.0 kernel
Date: Thu, 8 Feb 2001 04:18:14 +0100 [thread overview]
Message-ID: <20010208041814.I27027@suse.de> (raw)
In-Reply-To: <CDF99E351003D311A8B0009027457F1403BF9CA2@ausxmrr501.us.dell.com>
In-Reply-To: <CDF99E351003D311A8B0009027457F1403BF9CA2@ausxmrr501.us.dell.com>; from Matt_Domsch@Dell.com on Wed, Feb 07, 2001 at 09:03:53PM -0600
On Wed, Feb 07 2001, Matt_Domsch@Dell.com wrote:
> Adaptec is still working on it. Basically (and as Jason discovered), the
> driver and firmware can't handle single I/O requests larger than 64KB. Even
> when scatter/gathered, if the total is >64KB, it chokes. This was just fine
> for 2.2.x (no one has ever run into this problem there), but the
> much-improved block layer of 2.4.x throws larger I/Os at the driver. So,
> the developers at Adaptec are busy trying to add support to break large
> requests into smaller chunks, and then gather them back together.
Poor hardware, even IDE does better than this with scatter gather.
However, that's not why I'm replying. A driver should never have
to deal with bigger requests than it can handle. This just leads
to duplicated code in the block drivers and someone getting it
wrong (in fact, 2.4.1-pre showed bugs in the cpqarray driver
doing this for sg). The block layer is flexible enough to stop
merging beyond the low level drivers limit.
I haven't seen this driver, but if it uses the SCSI layer instead
of being a "pure" block driver then I can see a slight problem
in that currently only understand max sg entry limits and not
total request sizes. I would rather fix this limitation then, and
would also be interested to know if any of the (older) SCSI drivers
have such limitations too.
--
Jens Axboe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-08 3:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 3:03 aacraid 2.4.0 kernel Matt_Domsch
2001-02-08 3:18 ` Jens Axboe [this message]
2001-02-08 8:13 ` Alan Cox
2001-02-08 14:56 ` Jens Axboe
2001-02-08 8:09 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-02-08 3:24 Matt_Domsch
2001-02-08 3:28 ` Jens Axboe
2001-02-07 22:23 Jason Ford
2001-02-07 22:47 ` Byron Stanoszek
2001-02-08 0:37 ` Jason Ford
2001-02-08 0:55 ` Byron Stanoszek
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=20010208041814.I27027@suse.de \
--to=axboe@suse.de \
--cc=Matt_Domsch@Dell.com \
--cc=gandalf@winds.org \
--cc=jason@heymax.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