From: Jens Axboe <axboe@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: '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: Wed, 20 Oct 2004 17:58:25 +0200 [thread overview]
Message-ID: <20041020155825.GP10531@suse.de> (raw)
In-Reply-To: <1098287481.2008.6.camel@mulgrave>
On Wed, Oct 20 2004, James Bottomley wrote:
> On Wed, 2004-10-20 at 10:07, Jens Axboe wrote:
> > > Strange how this survived so long, thanks for debugging this James. The
> > > patch does look a little hackish, I'll see if I can beat it into
> > > submission.
>
> That's polite of you ... but you know it was my fault from the last
> round of IOMMU merges ...
Actually it didn't cross my mind, but now you've politely reminded
everyone :-)
> > Should this be enough to fix it?
> >
> > ===== drivers/block/ll_rw_blk.c 1.273 vs edited =====
> > --- 1.273/drivers/block/ll_rw_blk.c 2004-10-19 11:40:18 +02:00
> > +++ edited/drivers/block/ll_rw_blk.c 2004-10-20 17:06:12 +02:00
> > @@ -922,9 +922,10 @@
> > }
> > new_segment:
> > if (BIOVEC_VIRT_MERGEABLE(bvprv, bv) &&
> > - !BIOVEC_VIRT_OVERSIZE(hw_seg_size + bv->bv_len)) {
> > + !BIOVEC_VIRT_OVERSIZE(hw_seg_size + bv->bv_len) &&
> > + hw_seg_size + bv->bv_len <= q->max_segment_size)
> > hw_seg_size += bv->bv_len;
> > - } else {
> > + else {
> > new_hw_segment:
> > if (hw_seg_size > bio->bi_hw_front_size)
> > bio->bi_hw_front_size = hw_seg_size;
>
> This piece is actually contamination from my tree. Since
> q->max_segment_size is supposed to represent the parameters of the
> actual card sg descriptor table, and hence cannot theoretically be
> exceeded on either phys or virt merges, there's currently no way to
> communicate this parameter to the iommu, so the dma mapping will violate
> it even if the block layer respects it. We're just lucky most cards
> (barring ide ones which have their own hack) have 32 bit DMA length
> descriptors.
Ah yes, now I remember. How is the fix for that coming along, btw?
> > @@ -2766,22 +2767,36 @@
> > {
> > struct bio *bio, *prevbio = NULL;
> > int nr_phys_segs, nr_hw_segs;
> > + unsigned int phys_size, hw_size;
> > + request_queue_t *q = rq->q;
> >
> > if (!rq->bio)
> > return;
> >
> > - nr_phys_segs = nr_hw_segs = 0;
> > + phys_size = hw_size = nr_phys_segs = nr_hw_segs = 0;
> > rq_for_each_bio(bio, rq) {
> > /* Force bio hw/phys segs to be recalculated. */
> > bio->bi_flags &= ~(1 << BIO_SEG_VALID);
> >
> > - nr_phys_segs += bio_phys_segments(rq->q, bio);
> > - nr_hw_segs += bio_hw_segments(rq->q, bio);
> > + nr_phys_segs += bio_phys_segments(q, bio);
> > + nr_hw_segs += bio_hw_segments(q, bio);
> > if (prevbio) {
> > - if (blk_phys_contig_segment(rq->q, prevbio, bio))
> > + int pseg = phys_size + prevbio->bi_size + bio->bi_size;
> > + int hseg = hw_size + prevbio->bi_size + bio->bi_size;
> > +
> > + if (blk_phys_contig_segment(q, prevbio, bio) &&
> > + pseg <= q->max_segment_size) {
> > nr_phys_segs--;
> > - if (blk_hw_contig_segment(rq->q, prevbio, bio))
> > + phys_size += prevbio->bi_size + bio->bi_size;
> > + } else
> > + phys_size = 0;
> > +
> > + if (blk_hw_contig_segment(q, prevbio, bio) &&
> > + hseg <= q->max_segment_size) {
> > nr_hw_segs--;
> > + hw_size += prevbio->bi_size + bio->bi_size;
> > + } else
> > + hw_size = 0;
> > }
> > prevbio = bio;
> > }
>
> Yes, that looks much better ... thanks! I was plotting to enhance this
> later to use bi_hw_front_size and bi_hw_back_size, but not until we get
> the IOMMU descriptor length issue sorted out.
Agree, so I'll just push this to Andrew right away. Thanks for checking.
--
Jens Axboe
next prev parent reply other threads:[~2004-10-20 15:59 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 [this message]
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
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=20041020155825.GP10531@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@SteelEye.com \
--cc=dmo@osdl.org \
--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).