From: Jens Axboe <axboe@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, 'Dave Olien' <dmo@osdl.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] fix for Incorrect number of segments after building list problem
Date: Thu, 21 Oct 2004 15:02:19 +0200 [thread overview]
Message-ID: <20041021130218.GL10531@suse.de> (raw)
In-Reply-To: <1098362947.1777.1.camel@mulgrave>
On Thu, Oct 21 2004, James Bottomley wrote:
> On Wed, 2004-10-20 at 13:47, Jens Axboe wrote:
> > On Wed, Oct 20 2004, Jeff Garzik wrote:
> > > Clearly we need to remedy this :)
>
> Shamelessly beg for hardware? Moi? How well^Wlittle you know me.
Hehe
> > By improving James' imagination? :)
>
> I meant that 50% of the fix is pulling out the hacks that permeate the
> IDE drivers to resplit SG lists after iommu merging. That's the bit I
> can't test.
That's true. But you could set the same limits for SCSI, and check in
init_io() whether those limits are violated.
But I should shut up, I don't want to ruin your chance at free hardware.
SCSI whore gone SATA, so sad :)
--
Jens Axboe
prev parent reply other threads:[~2004-10-21 13:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 21:51 [PATCH] fix for Incorrect number of segments after building list problem James Bottomley
2004-10-14 21:55 ` 'Dave Olien'
2004-10-14 22:15 ` 'Dave Olien'
2004-10-14 22:51 ` 'Dave Olien'
2004-10-20 14:39 ` Jens Axboe
2004-10-20 15:07 ` Jens Axboe
2004-10-20 15:50 ` James Bottomley
2004-10-20 15:58 ` Jens Axboe
2004-10-20 16:07 ` James Bottomley
2004-10-20 16:11 ` Jens Axboe
2004-10-20 17:45 ` Jeff Garzik
2004-10-20 17:47 ` Jens Axboe
2004-10-20 18:11 ` Jeff Garzik
2004-10-21 12:49 ` James Bottomley
2004-10-21 13:02 ` Jens Axboe [this message]
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=20041021130218.GL10531@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@SteelEye.com \
--cc=dmo@osdl.org \
--cc=jgarzik@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).