From: Christoph Hellwig <hch@infradead.org>
To: Johannes Thumshirn <jthumshirn@suse.de>
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 02:05:25 -0800 [thread overview]
Message-ID: <20160125100525.GA24369@infradead.org> (raw)
In-Reply-To: <1453470088-43959-1-git-send-email-jthumshirn@suse.de>
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.
Anything that prolongs the misery of keeping the old request code around
is a bad idea.
> 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.
next prev parent reply other threads:[~2016-01-25 10:05 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 [this message]
2016-01-25 10:16 ` Johannes Thumshirn
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=20160125100525.GA24369@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=buchino@cisco.com \
--cc=dick.kennedy@avagotech.com \
--cc=hare@suse.de \
--cc=hiralpat@cisco.com \
--cc=james.smart@avagotech.com \
--cc=jthumshirn@suse.de \
--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 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).