public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christof Schmitt <christof.schmitt@de.ibm.com>
To: James Smart <James.Smart@Emulex.Com>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: queue_depth tracking from LLD
Date: Thu, 16 Apr 2009 17:27:07 +0200	[thread overview]
Message-ID: <20090416152707.GA18972@schmichrtp.de.ibm.com> (raw)
In-Reply-To: <49E742CE.3020302@emulex.com>

On Thu, Apr 16, 2009 at 10:38:06AM -0400, James Smart wrote:
> Mike Christie wrote:
[...]
> No good reason.  It should be in the midlayer, and that was the
> recommendation I made at storage summit a couple of years ago. It
> hasn't as, for the drivers that  care, they had already implemented
> it. It also isn't a relished task, as there will be lots of
> discussion on how the ramp-up should be implemented - which may
> mean, the need for more  algorithms.

zfcp is one of the drivers that don't have ramp-up/down mechanism in
place. And i am trying to understand what is required here.  Is there
currently work being done to get queue_depth ramp-up/down in the
midlayer?

>> If we moved code like that to the scsi layer, then is all the is needed 
>> is a interface to config this?

> Yep. As mentioned, figuring out what algorithm, for what device and
> configuration, will be the more interesting thing.

If the LLDs that currently have a private ramp-up/down mechanism in
place use a similar strategy, would it make sense to first move them
to common code that can be activated from a LLD? And later refine it
with device-specific behaviour?

--
Christof Schmitt

  reply	other threads:[~2009-04-16 15:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16  9:36 queue_depth tracking from LLD Christof Schmitt
2009-04-16 14:13 ` James Smart
2009-04-16 14:27   ` Mike Christie
2009-04-16 14:38     ` James Smart
2009-04-16 15:27       ` Christof Schmitt [this message]
2009-04-16 15:32         ` James Smart
2009-04-16 14:33   ` Matthew Wilcox
2009-04-16 14:40     ` James Smart

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=20090416152707.GA18972@schmichrtp.de.ibm.com \
    --to=christof.schmitt@de.ibm.com \
    --cc=James.Smart@Emulex.Com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /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