From: Christoph Hellwig <hch@lst.de>
To: Stephen Cameron <stephenmcameron@gmail.com>
Cc: "Elliott, Robert (Server Storage)" <Elliott@hp.com>,
Hannes Reinecke <hare@suse.de>,
"Stephen M. Cameron" <scameron@beardog.cce.hp.com>,
"james.bottomley@parallels.com" <james.bottomley@parallels.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 18:17:21 +0200 [thread overview]
Message-ID: <20140726161721.GA6743@lst.de> (raw)
In-Reply-To: <CADzpL0Rn+x6N=v123EBej_iZhTwmjMYZ4deeTeRG7_sxgXU9PQ@mail.gmail.com>
On Sat, Jul 26, 2014 at 11:14:35AM -0500, Stephen Cameron wrote:
> Hmm, I forgot that that patch was in there, I wasn't trying to keep pushing
> it along. From the previous discussion, I got the impression I was simply
> wrong, and that this patch wasn't needed, so I had meant to drop it, I just
> forgot to actually drop it.
It's more complicated - as Robert indicated you're tenically right, although
in practice it's not what the existing users expect. If you have some
cycles for it I'd love to at lest get the per-LUN and per-target
ramp up/down in ASAP. We can then start looking into doing it even
better based on the target response later on.
next prev parent reply other threads:[~2014-07-26 16:17 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
[not found] ` <CADzpL0Rn+x6N=v123EBej_iZhTwmjMYZ4deeTeRG7_sxgXU9PQ@mail.gmail.com>
2014-07-26 16:17 ` Christoph Hellwig [this message]
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=20140726161721.GA6743@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.