public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
Cc: Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>,
	"Stephen M. Cameron" <scameron@beardog.cce.hp.com>,
	"james.bottomley@parallels.com" <james.bottomley@parallels.com>,
	"stephenmcameron@gmail.com" <stephenmcameron@gmail.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Vasu Dev <vasu.dev@linux.intel.com>,
	Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: [PATCH] scsi: break from queue depth adjusting loops when device found
Date: Sat, 26 Jul 2014 17:36:12 +0200	[thread overview]
Message-ID: <20140726153612.GA6513@lst.de> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B402958B86659@G9W0745.americas.hpqcorp.net>

I just saw this patch showing up again in the hpsa series, so let's get
the discussiong going on how to proceed again:

I think we can't simply apply the current version as it breaks the intended
semantics in the FC drivers that expect an array with target-wide ressources.

So if we want to go ahead quickly we might just need two versions of it, one
that does LUN-level ramp up/down and one that does target level.

I'd also very much like to be able to use the SAM-4 indicators, but I fear
that a lot of hardware might not be able to get this right.  If anyone
has experience with using those I'd love to hear about it.

  parent reply	other threads:[~2014-07-26 15:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 15:05 [PATCH] scsi: break from queue depth adjusting loops when device found Stephen M. Cameron
2014-07-03 15:25 ` Douglas Gilbert
2014-07-03 17:11 ` Christoph Hellwig
2014-07-03 17:21   ` Mike Christie
2014-07-04 18:36     ` Douglas Gilbert
2014-07-04 10:53   ` Hannes Reinecke
2014-07-04 19:21     ` Elliott, Robert (Server Storage)
2014-07-06  9:49       ` Christoph Hellwig
2014-07-26 15:36       ` Christoph Hellwig [this message]
     [not found]         ` <CADzpL0Rn+x6N=v123EBej_iZhTwmjMYZ4deeTeRG7_sxgXU9PQ@mail.gmail.com>
2014-07-26 16:17           ` Christoph Hellwig
2014-07-27 15:36             ` Hannes Reinecke

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=20140726153612.GA6513@lst.de \
    --to=hch@lst.de \
    --cc=Elliott@hp.com \
    --cc=hare@suse.de \
    --cc=james.bottomley@parallels.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=scameron@beardog.cce.hp.com \
    --cc=stephenmcameron@gmail.com \
    --cc=vasu.dev@linux.intel.com \
    /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