From: Hans de Goede <hdegoede@redhat.com>
To: linux-usb <linux-usb@vger.kernel.org>,
SCSI development list <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [REGRESSION 3.17] scsi (uas) disks no longer using tagged command queuing
Date: Tue, 09 Sep 2014 11:15:24 +0200 [thread overview]
Message-ID: <540EC52C.3000804@redhat.com> (raw)
Hi All,
While working on making error handling in the uas driver more robust,
I noticed that all the commands being send to a sata ssd hooked up
over uas were untagged, where I would expect tcq to be used, as that
is the big advantage of uas over usb-storage / bot.
Taking the uas.c file from 3.17, and building it for 3.16 restores
the use of tcq (debugged by adding a printk blk_rq_tagged + request->tag).
So either uas is doing something wrong which happened to work in
3.16, or something has broken in 3.17.
I've already added debug printk-s of scsi_device->tagged_supported,
queue_depth, ordered_tags and simple_tags and those all look good
(1, 29, 1, 1).
I've also tried setting disable_blk_mq and that does not help.
Any hints to help debugging this further (other then a bisect) are
appreciated. If no-one has any smart ideas I guess I'll end up doing
a full bisect.
Regards,
Hans
next reply other threads:[~2014-09-09 9:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 9:15 Hans de Goede [this message]
2014-09-09 15:27 ` [REGRESSION 3.17] scsi (uas) disks no longer using tagged command queuing Christoph Hellwig
2014-09-10 7:21 ` Hans de Goede
2014-09-10 15:45 ` Christoph Hellwig
2014-09-11 10:01 ` Hans de Goede
2014-09-11 16:13 ` Christoph Hellwig
2014-09-12 19:49 ` Hans de Goede
2014-09-12 23:00 ` [PATCH] scsi: fix regression that accidentally disabled block-based tcq Christoph Hellwig
2014-09-13 10:28 ` Hans de Goede
2014-09-13 17:50 ` Christoph Hellwig
2014-09-14 9:41 ` Hans de Goede
2014-09-15 18:47 ` review-ping: " Christoph Hellwig
2014-09-15 19:05 ` Webb Scales
2014-09-15 19:15 ` Hans de Goede
2014-09-15 19:39 ` Jeff Moyer
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=540EC52C.3000804@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@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).