From: Jens Axboe <axboe@kernel.dk>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: 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: Thu, 18 Jul 2013 18:30:34 -0600 [thread overview]
Message-ID: <20130719003034.GG28005@kernel.dk> (raw)
In-Reply-To: <1374193399.7397.973.camel@haakon3.risingtidesystems.com>
On Thu, Jul 18 2013, Nicholas A. Bellinger wrote:
> On Thu, 2013-07-18 at 13:12 -0600, Mike Christie wrote:
> > On 07/18/2013 12:51 PM, Nicholas A. Bellinger wrote:
> > > On Wed, 2013-07-17 at 18:19 +0200, Alexander Gordeev wrote:
> > >> On Tue, Jul 16, 2013 at 02:38:03PM -0700, Nicholas A. Bellinger wrote:
> > >>> [ 7.927818] scsi_execute(): Calling blk_mq_free_request >>>
> > >>> [ 7.927826] scsi 0:0:0:0: Direct-Access ATA ST9500530NS CC03 PQ: 0 ANSI: 5
> > >>>
> > >>> OK, so INQUIRY response payload is looking as expected here.
> > >>
> > >> Yep. It is not on the top of my head, but I remember something like INQUIRYs
> > >> are emulated and thus do not have payload.
> > >>
> > >>> [ 7.927960] sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
> > >>> [ 7.927964] sd 0:0:0:0: [sda] 1 512-byte logical blocks: (512 B/512 B)
> > >>> [ 7.927965] sd 0:0:0:0: [sda] 0-byte physical blocks
> > >>>
> > >>> Strange.. READ_CAPACITY appears to be returning a payload as zeros..?
> > >>
> > >> Yep. Because blk_execute_rq() does not put the proper callback and data do
> > >> not get copied from sg's to bounce buffer. That is why I tried to use
> > >> blk_mq_execute_rq() instead. Once I do that, data start getting read and
> > >> booting stops elsewhere.
> > >
> > > Mmmmmm.
> > >
> > > The call to blk_queue_bounce() exists within blk_mq_make_request(), but
> > > AFAICT this should still be getting invoked regardless of if the struct
> > > request is dispatched into blk-mq via the modified blk_execute_rq() ->
> > > blk_execute_rq_nowait() -> blk_mq_insert_request() codepath, or directly
> > > via blk_mq_execute_rq()..
> > >
> >
> > blk_mq_make_request is not called from the blk insert/execute paths.
> > blk_mq_make_request takes a bio and tries to merge it with a request and
> > adds it to the queue. It is only called when the make_request_fn is
> > called like when generic_make_request is called.
> >
> > blk_mq_insert_request adds a already formed request to the queue. It is
> > already formed so that is why that path does not bounce bios. The
> > bios/pages should already be added within the drivers restrictions. So
> > for the read_cap path, the call to blk_rq_map_kern in scsi_execute does
> > the blk_queue_bounce call.
> >
>
> <nod>, just noticed the blk_queue_bounce() in blk_rq_map_kern().
>
> Not sure why this doesn't seem to be doing what it's supposed to for
> libata just yet..
How are you make the request from the bio? It'd be pretty trivial to
ensure that it gets bounced properly... blk_mq_execute_rq() assumes a
fully complete request, so it wont bounce anything.
--
Jens Axboe
next prev parent reply other threads:[~2013-07-19 0:30 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 19:00 [PATCH RESEND 0/1] AHCI: Optimize interrupt processing 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 [this message]
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
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=20130719003034.GG28005@kernel.dk \
--to=axboe@kernel.dk \
--cc=agordeev@redhat.com \
--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=nab@linux-iscsi.org \
--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;
as well as URLs for NNTP newsgroup(s).