From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Jeff Garzik <jgarzik@pobox.com>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH RESEND 0/1] AHCI: Optimize interrupt processing
Date: Fri, 12 Jul 2013 22:20:12 -0700 [thread overview]
Message-ID: <1373692812.7397.625.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <20130712074559.GA8727@dhcp-26-207.brq.redhat.com>
On Fri, 2013-07-12 at 09:46 +0200, Alexander Gordeev wrote:
> On Thu, Jul 11, 2013 at 04:00:37PM -0700, Nicholas A. Bellinger wrote:
> > On Thu, 2013-07-11 at 12:26 +0200, Alexander Gordeev wrote:
> > > On Wed, May 22, 2013 at 07:03:05PM +0200, Jens Axboe wrote:
> > > > On Wed, May 22 2013, Alexander Gordeev wrote:
> > > > > On Wed, May 22, 2013 at 08:50:03AM +0900, Tejun Heo wrote:
> > > > > > Hmmmmmm..... I'd normally apply this patch but block layer is just
> > > > > > growing multi-queue support and libata is likely to be converted to mq
> > > > > > in foreseeable future, so I'm a bit hesitant to make irq handling more
> > > > > > sophiscated right now. Would you be interested in looking into
> > > > > > converting libata to blk mq support? I'm pretty sure it'd yield far
> > > > > > better outcome if done properly.
> > > > >
> > > > > I am not committing, but will look into it, sure.
> > > >
> > > > Would be most awesome, I'm sure Nic would not mind a bit of help on the
> > > > SCSI/libata side :-)
> > >
> > > Hi Nicholas,
> > >
> > > Could you please clarify the status of SCSI MQ support? Is it usable now?
> > >
> >
> > Hi Alexander,
> >
> > Thanks for taking a look. I've not made further progress in the last
> > weeks on scsi-mq, but am still using virtio-scsi + scsi-mq <->
> > vhost-scsi + per-cpu-ida for quite a bit for benchmarking purposes.
>
> Thanks for the clarification, Nicholas.
>
> > > I tried git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git,
> > > but it does not appear working without (at least) changes below to SCSI lib:
> > >
> >
> > The only scsi-mq LLD conversions so far have been to virtio-scsi +
> > scsi_debug to nop REQ_TYPE_FS.
>
> I see. Do you think the changes I made is a right way to go?
>
> I had to make it to avoid a NULL-pointer assignent and make BIO bounce
> buffers work, but I do not really understand the mixture of old and
> new code ( neither in fact :) )
>
Hi Alexander,
Comments below.
> > Just so I understand, your patch below is required in order to make what
> > LLD function with scsi-mq..?
>
> ata_piix
>
<nod>
> >
> > Thanks!
> >
> > --nab
> >
> > > Thanks!
> > >
> > > diff --git a/drivers/scsi/scsi-mq.c b/drivers/scsi/scsi-mq.c
> > > index ca6ff67..d8cc7a4 100644
> > > --- a/drivers/scsi/scsi-mq.c
> > > +++ b/drivers/scsi/scsi-mq.c
> > > @@ -155,6 +155,7 @@ void scsi_mq_done(struct scsi_cmnd *sc)
> > > static struct blk_mq_ops scsi_mq_ops = {
> > > .queue_rq = scsi_mq_queue_rq,
> > > .map_queue = blk_mq_map_queue,
> > > + .timeout = scsi_times_out,
> > > .alloc_hctx = blk_mq_alloc_single_hw_queue,
> > > .free_hctx = blk_mq_free_single_hw_queue,
> > > };
So your actually triggering a blk-mq timeout with ata_piix..?
> > > diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
> > > index 65360db..33aa373 100644
> > > --- a/drivers/scsi/scsi_lib.c
> > > +++ b/drivers/scsi/scsi_lib.c
> > > @@ -283,7 +283,10 @@ int scsi_execute(struct scsi_device *sdev, const unsigned char *cmd,
> > > /*
> > > * head injection *required* here otherwise quiesce won't work
> > > */
> > > - blk_execute_rq(req->q, NULL, req, 1);
> > > + if (q->mq_ops)
> > > + blk_mq_execute_rq(req->q, req);
> > > + else
> > > + blk_execute_rq(req->q, NULL, req, 1);
> > >
The scsi_execute() -> REQ_TYPE_BLOCK_RQ special case (scsi_scan +
scsi_ioctl) has a small issue preventing it's conversion to use
blk_mq_execute_rq().
Namely that scsi_execute_cmd() currently expects to be able to check for
the existence of req->errors + req->resid_len *after*
blk_mq_execute_rq() -> blk_mq_finish_request() -> blk_mq_free_request()
has been called to mark the pre-allocated struct request as free for
blk-mq re-use.
That is why scsi-mq still uses blk_execute_rq() for this reason, and
this will need be addressed in order to safely use blk_mq_execute_rq()
in the above context.
> > > /*
> > > * Some devices (USB mass-storage in particular) may transfer
> > > @@ -298,12 +301,8 @@ int scsi_execute(struct scsi_device *sdev, const unsigned char *cmd,
> > > *resid = req->resid_len;
> > > ret = req->errors;
> > > out:
> > > - if (q->mq_ops) {
> > > - printk("scsi_execute(): Calling blk_mq_free_request >>>\n");
> > > - blk_mq_free_request(req);
> > > - } else {
> > > + if (!q->mq_ops)
> > > blk_put_request(req);
> > > - }
> > >
Do you have an OOPs backtrace handy to post w/o the last two changes in
place..?
Also, just a heads up that so far I've been using IDE (/dev/hdX) for the
root-device in order to make scsi-mq debugging safer and easier.
I *very* much recommend doing the same if at all possible for ata_piix
scsi-mq development + testing, as you'll want to be very careful when
using a real file-system on top of this early alpha code.
--nab
next prev parent reply other threads:[~2013-07-13 5:15 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 [this message]
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
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=1373692812.7397.625.camel@haakon3.risingtidesystems.com \
--to=nab@linux-iscsi.org \
--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=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®