linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@lst.de>,
	linux-scsi@vger.kernel.org,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Robert Elliott <elliott@hp.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Bart van Assche <bvanassche@acm.org>, Jens Axboe <axboe@fb.com>,
	Kashyap Desai <kashyap.desai@avagotech.com>,
	Sreekanth Reddy <sreekanth.reddy@avagotech.com>,
	Mike Christie <michaelc@cs.wisc.edu>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	usb-storage@lists.one-eyed-alien.net
Subject: Re: [PATCH 08/11] scsi: always assign block layer tags if enabled
Date: Tue, 4 Nov 2014 11:42:16 +0100	[thread overview]
Message-ID: <20141104104216.GD19154@lst.de> (raw)
In-Reply-To: <545895E0.1000902@suse.de>

On Tue, Nov 04, 2014 at 10:01:20AM +0100, Hannes Reinecke wrote:
> Hmm. With patch 03/11 and 04/11 you've removed the ordered_tags
> fields, on the ground that the block layer never issues ordered tags
> nowadays.
> Yet these drivers still try to activate ordered tags.
> So what's happening here?

Broken APIs - in the current tree we can set the ->ordered_tags
field through scsi_adjust_queue_depth and scsi_set_tag_type, but that
field isn't ever checked except for the queue_type sysfs file and
a few pintks.

> Do these drivers switch on ordered tags on their own?
> If so, why shouldn't the other drivers (like the various FC HBAs) be
> allowed to do it, too?
> Shouldn't we rather remove ordered tagging from those drivers, too?

Except for a few SPI drivers that issue an ordered tag on their own
every N commands to avoid locking devices up ordered tag support
is gone from the tree (at least on the initiator side).

> (Although I'm not too happy about removing ordered tags support in
> the other drivers. I have the nagging feeling they might become
> important if and when ZBC ever gets off the ground ...)

Good luck with that mess.  It will have to look very different anyway if
it should be remotely supportable, and would be limited to a small
set of hardware currently not pretending to have ordered tag support
(SAS + SATA basically).

  reply	other threads:[~2014-11-04 10:42 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04  7:54 tag handling refactor Christoph Hellwig
2014-11-04  7:54 ` [PATCH 01/11] scsi: provide a generic change_queue_type method Christoph Hellwig
2014-11-04  8:26   ` Hannes Reinecke
2014-11-05  2:09   ` Martin K. Petersen
2014-11-06 15:28   ` Bart Van Assche
2014-11-06 15:35     ` Christoph Hellwig
2014-11-04  7:54 ` [PATCH 02/11] scsi: add new scsi-command flag for tagged commands Christoph Hellwig
2014-11-04  8:38   ` Hannes Reinecke
2014-11-04 10:35     ` Christoph Hellwig
2014-11-04 10:44       ` Hannes Reinecke
2014-11-05  2:12   ` Martin K. Petersen
2014-11-04  7:54 ` [PATCH 03/11] scsi: remove ordered_tags scsi_device field Christoph Hellwig
2014-11-05  2:14   ` Martin K. Petersen
2014-11-06 15:44   ` Bart Van Assche
2014-11-04  7:54 ` [PATCH 04/11] scsi: remove ordered_tag host template field Christoph Hellwig
2014-11-04  8:38   ` Hannes Reinecke
2014-11-05  2:15   ` Martin K. Petersen
2014-11-06 15:45   ` Bart Van Assche
2014-11-04  7:54 ` [PATCH 05/11] scsi: remove abuses of scsi_populate_tag Christoph Hellwig
2014-11-04  8:45   ` Hannes Reinecke
2014-11-04 10:37     ` Christoph Hellwig
2014-11-04  7:54 ` [PATCH 06/11] mptfusion: don't change queue type in ->change_queue_depth Christoph Hellwig
2014-11-04  8:46   ` Hannes Reinecke
2014-11-05  2:17   ` Martin K. Petersen
2014-11-04  7:54 ` [PATCH 07/11] scsi: remove use_blk_tcq Scsi_Host field Christoph Hellwig
2014-11-04  8:46   ` Hannes Reinecke
2014-11-05  2:18   ` Martin K. Petersen
2014-11-04  7:54 ` [PATCH 08/11] scsi: always assign block layer tags if enabled Christoph Hellwig
2014-11-04  9:01   ` Hannes Reinecke
2014-11-04 10:42     ` Christoph Hellwig [this message]
2014-11-04 10:46       ` Hannes Reinecke
2014-11-05  2:32   ` Martin K. Petersen
2014-11-05  2:34     ` Martin K. Petersen
2014-11-06 16:28   ` Bart Van Assche
2014-11-06 16:31     ` Christoph Hellwig
2014-11-04  7:54 ` [PATCH 09/11] scsi: don't set tagging state from scsi_adjust_queue_depth Christoph Hellwig
2014-11-04  9:26   ` Hannes Reinecke
2014-11-04 10:47     ` Christoph Hellwig
2014-11-05  2:50   ` Martin K. Petersen
2014-11-04  7:54 ` [PATCH 10/11] scsi: don't force tagged_supported in drivers Christoph Hellwig
2014-11-04  8:16   ` Jack Wang
2014-11-04 10:34     ` Christoph Hellwig
2014-11-04  7:54 ` [PATCH 11/11] ufs: remove spurious scsi_set_tag_type call Christoph Hellwig
2014-11-05 19:26 ` tag handling refactor Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2014-11-10 15:56 tag handling refactor V2 Christoph Hellwig
2014-11-10 15:56 ` [PATCH 08/11] scsi: always assign block layer tags if enabled Christoph Hellwig

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=20141104104216.GD19154@lst.de \
    --to=hch@lst.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=axboe@fb.com \
    --cc=bvanassche@acm.org \
    --cc=elliott@hp.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=hare@suse.de \
    --cc=kashyap.desai@avagotech.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=michaelc@cs.wisc.edu \
    --cc=sreekanth.reddy@avagotech.com \
    --cc=usb-storage@lists.one-eyed-alien.net \
    /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).