From: Johannes Thumshirn <jthumshirn@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Hiral Patel <hiralpat@cisco.com>, Suma Ramars <sramars@cisco.com>,
Brian Uchino <buchino@cisco.com>,
James Smart <james.smart@avagotech.com>,
Dick Kennedy <dick.kennedy@avagotech.com>,
Hannes Reinecke <hare@suse.de>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: Allow activation of scsi-mq per-driver
Date: Mon, 25 Jan 2016 11:16:14 +0100 [thread overview]
Message-ID: <20160125101614.GD29561@c203.arch.suse.de> (raw)
In-Reply-To: <20160125100525.GA24369@infradead.org>
On Mon, Jan 25, 2016 at 02:05:25AM -0800, Christoph Hellwig wrote:
> On Fri, Jan 22, 2016 at 02:41:28PM +0100, Johannes Thumshirn wrote:
> > Allow the activation of the scsi-mq feature on a per-driver bassis as opposed
> > to the current stack global (de)activation.
> >
> > This allows us to have setups which can combine "slow" rotational media and
> > fast media on two different HBA types.
>
> It's still the wrong thing to do. One of your co-workers has been
> working on slicing for blk-mq to better support slower adapters.
I know but there are no results yet.
>
> Anything that prolongs the misery of keeping the old request code around
> is a bad idea.
Agreed, but this patch is a "quick fix" for the problem until the nice solution
is in place. The way it currently works is unacceptable from a distribution
point of view.
>
> > The following is from a host with rotational disks behind a HP SAS Adapter and
> > a fibre channel array behind a Emulex FC Adapter. The hpsa driver does not
> > support scsi-mq yet (and has rotational disks attached to it), but the lpfc
> > does. This patch allows an optimal combination of the scsi-mq enabled lpfc
> > driver and the hpsa driver which still uses a single queue scsi layer and thus
> > can make use of IO schedulers.
>
> And this is another reason why this is bad. There are very slow dumb
> FC array arounds as well as really fast ones. And there are really slow
> SATA disks behind SAS controllers as well as really fast SSDs.
>
> The host is simply the wrong place to decide these things.
Yes, but this way the admin can _decide_ on which driver's he/she is going to
activate scsi-mq and on which not. Of casue this only solves the issue if
multiple drivers are involved, but still better than a global on/off switch.
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-01-25 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 13:41 [PATCH] scsi: Allow activation of scsi-mq per-driver Johannes Thumshirn
2016-01-22 13:43 ` Hannes Reinecke
2016-01-25 10:05 ` Christoph Hellwig
2016-01-25 10:16 ` Johannes Thumshirn [this message]
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=20160125101614.GD29561@c203.arch.suse.de \
--to=jthumshirn@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=buchino@cisco.com \
--cc=dick.kennedy@avagotech.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=hiralpat@cisco.com \
--cc=james.smart@avagotech.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sramars@cisco.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.