From: Christoph Hellwig <hch@infradead.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: SCSI development list <linux-scsi@vger.kernel.org>,
Douglas Gilbert <dgilbert@interlog.com>
Subject: Re: uas breakage when using scsi_mod.blk_mq=Y
Date: Wed, 1 Oct 2014 10:31:05 -0700 [thread overview]
Message-ID: <20141001173105.GA4193@infradead.org> (raw)
In-Reply-To: <542C2366.30700@redhat.com>
On Wed, Oct 01, 2014 at 05:53:10PM +0200, Hans de Goede wrote:
> So let me see if I understand this correctly, blk-mq will never queue
> more then qdepth commands, but it will use higher tag numbers ?
Correct.
> If that is the case fixing this should be easy, uas already has
> an array to map stream-ids to scsi cmnds so that when it gets a status
> urb, it can find the scsi cmnd which belongs to that status urb. We
> can just search for a free slot in that array.
That sounds good.
prev parent reply other threads:[~2014-10-01 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 8:17 uas breakage when using scsi_mod.blk_mq=Y Hans de Goede
2014-10-01 12:45 ` Christoph Hellwig
2014-10-01 15:53 ` Hans de Goede
2014-10-01 17:31 ` Christoph Hellwig [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=20141001173105.GA4193@infradead.org \
--to=hch@infradead.org \
--cc=dgilbert@interlog.com \
--cc=hdegoede@redhat.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