From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Mike Christie <michaelc@cs.wisc.edu>,
Alexander Gordeev <agordeev@redhat.com>,
Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Jeff Garzik <jgarzik@pobox.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH RESEND 0/1] AHCI: Optimize interrupt processing
Date: Fri, 19 Jul 2013 21:56:02 -0700 [thread overview]
Message-ID: <1374296162.7397.1098.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <1374267684.7397.1058.camel@haakon3.risingtidesystems.com>
On Fri, 2013-07-19 at 14:01 -0700, Nicholas A. Bellinger wrote:
> On Fri, 2013-07-19 at 08:33 -0700, James Bottomley wrote:
> > On Thu, 2013-07-18 at 23:34 -0700, Nicholas A. Bellinger wrote:
> > > diff --git a/drivers/ata/libata-scsi.c b/drivers/ata/libata-scsi.c
> > > index 0101af5..191bc15 100644
> > > --- a/drivers/ata/libata-scsi.c
> > > +++ b/drivers/ata/libata-scsi.c
> > > @@ -1144,7 +1144,11 @@ static int ata_scsi_dev_config(struct scsi_device *sdev,
> > > "sector_size=%u > PAGE_SIZE, PIO may malfunction\n",
> > > sdev->sector_size);
> > >
> > > - blk_queue_update_dma_alignment(q, sdev->sector_size - 1);
> > > + if (!q->mq_ops) {
> > > + blk_queue_update_dma_alignment(q, sdev->sector_size - 1);
> > > + } else {
> > > + printk("Skipping dma_alignment for libata w/ scsi-mq\n");
> > > + }
> >
> > Amazingly enough there is a reason for the dma alignment, and it wasn't
> > just to annoy you, so you can't blindly do this.
> >
> > The email thread is probably lost in the mists of time, but if I
> > remember correctly the problem is that some ahci DMA controllers barf if
> > the sector they're doing DMA on crosses a page boundary. Some are
> > annoying enough to actually cause silent data corruption. You won't
> > find every ahci DMA controller doing this, so the change will work for
> > some, but it will be hard to identify those it won't work for until
> > people start losing data.
>
> Thanks for the extra background.
>
> So at least from what I gather thus far this shouldn't be an issue for
> initial testing with scsi-mq <-> libata w/ ata_piix.
>
> >
> > The correct fix, obviously, is to do the bio copy on the kernel path for
> > unaligned data. It is OK to assume that REQ_TYPE_FS data is correctly
> > aligned (because of the block to page alignment).
> >
>
> Indeed. Looking into the bio_copy_kern() breakage next..
>
OK, after further investigation the root cause is a actually a missing
bio->bio_end_io() -> bio_copy_kern_endio() -> bio_put() from the
blk_end_sync_rq() callback path that scsi-mq REQ_TYPE_BLOCK_PC is
currently using.
Including the following patch into the scsi-mq working branch now, and
reverting the libata dma_alignment=0x03 hack.
Alexander, care to give this a try..?
--nab
diff --git a/block/blk-exec.c b/block/blk-exec.c
index 0761c89..70303d2 100644
--- a/block/blk-exec.c
+++ b/block/blk-exec.c
@@ -25,7 +25,10 @@ static void blk_end_sync_rq(struct request *rq, int error)
struct completion *waiting = rq->end_io_data;
rq->end_io_data = NULL;
- if (!rq->q->mq_ops) {
+ if (rq->q->mq_ops) {
+ if (rq->bio)
+ bio_endio(rq->bio, error);
+ } else {
__blk_put_request(rq->q, rq);
}
next prev parent reply other threads:[~2013-07-20 4:50 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 19:00 Alexander Gordeev
2013-05-21 19:00 ` [PATCH RESEND 1/1] " Alexander Gordeev
2013-05-21 23:50 ` [PATCH RESEND 0/1] " Tejun Heo
2013-05-22 14:39 ` Alexander Gordeev
2013-05-22 17:03 ` Jens Axboe
2013-07-11 10:26 ` Alexander Gordeev
2013-07-11 23:00 ` Nicholas A. Bellinger
2013-07-12 7:46 ` Alexander Gordeev
2013-07-13 5:20 ` Nicholas A. Bellinger
2013-07-16 18:32 ` Alexander Gordeev
2013-07-16 21:38 ` Nicholas A. Bellinger
2013-07-17 16:19 ` Alexander Gordeev
2013-07-18 18:51 ` Nicholas A. Bellinger
2013-07-18 19:12 ` Mike Christie
2013-07-19 0:23 ` Nicholas A. Bellinger
2013-07-19 0:30 ` Jens Axboe
2013-07-19 1:03 ` Nicholas A. Bellinger
2013-07-19 6:34 ` Nicholas A. Bellinger
2013-07-19 15:33 ` James Bottomley
2013-07-19 21:01 ` Nicholas A. Bellinger
2013-07-20 4:56 ` Nicholas A. Bellinger [this message]
2013-07-20 14:48 ` Mike Christie
2013-07-20 22:14 ` Nicholas A. Bellinger
2013-07-20 23:57 ` Jens Axboe
2013-08-09 19:15 ` Alexander Gordeev
2013-08-09 20:17 ` Nicholas A. Bellinger
2013-08-15 16:23 ` Alexander Gordeev
2013-08-16 2:19 ` Nicholas A. Bellinger
2013-08-16 16:41 ` Alexander Gordeev
2013-08-16 17:46 ` Nicholas A. Bellinger
2013-08-28 15:56 ` Alexander Gordeev
2013-09-20 15:19 ` Alexander Gordeev
2013-09-20 20:41 ` Nicholas A. Bellinger
2013-10-03 11:06 ` Christoph Hellwig
2013-10-07 14:44 ` Alexander Gordeev
2013-07-22 15:03 ` Alexander Gordeev
2013-07-22 21:10 ` Nicholas A. Bellinger
2013-07-25 10:16 ` Alexander Gordeev
2013-07-25 22:08 ` Nicholas A. Bellinger
2013-07-26 2:09 ` Jens Axboe
2013-07-26 21:14 ` Nicholas A. Bellinger
2013-07-27 0:43 ` Nicholas A. Bellinger
2013-07-29 11:18 ` Alexander Gordeev
2013-07-29 14:08 ` Jens Axboe
2013-07-29 19:19 ` Nicholas A. Bellinger
2013-07-31 4:16 ` Marc C
2013-07-31 10:23 ` Tejun Heo
2013-07-29 11:50 ` Tejun Heo
2013-07-29 19:11 ` Nicholas A. Bellinger
2013-07-29 11:46 ` Tejun Heo
2013-07-29 14:03 ` Jens Axboe
2013-08-09 8:23 ` Alexander Gordeev
2013-08-09 14:15 ` Tejun Heo
2013-08-09 14:24 ` Jens Axboe
2013-08-09 15:07 ` Alexander Gordeev
2013-08-09 15:52 ` Jens Axboe
2013-08-09 16:46 ` Alexander Gordeev
2013-08-09 17:07 ` Jens Axboe
2013-08-12 15:21 ` Alexander Gordeev
2013-07-29 7:28 ` Hannes Reinecke
2013-07-31 17:11 ` Alexander Gordeev
2013-07-19 15:58 ` Mike Christie
2013-07-19 21:05 ` Nicholas A. Bellinger
2013-07-18 19:14 ` Nicholas A. Bellinger
2013-07-18 21:21 ` Jens Axboe
2014-09-11 12:42 ` Alexander Gordeev
2014-09-11 12:44 ` [PATCH v2] " Alexander Gordeev
2014-09-13 4:43 ` Tejun Heo
2014-09-11 13:36 ` [PATCH RESEND 0/1] " Bartlomiej Zolnierkiewicz
2014-09-13 4:46 ` Tejun Heo
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=1374296162.7397.1098.camel@haakon3.risingtidesystems.com \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=agordeev@redhat.com \
--cc=axboe@kernel.dk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=tj@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
all inboxes | Powered by JetHome®