From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "hch@lst.de" <hch@lst.de>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] Revert "scsi: default to scsi-mq"
Date: Mon, 14 Aug 2017 15:21:06 +0000 [thread overview]
Message-ID: <1502724064.2333.5.camel@wdc.com> (raw)
In-Reply-To: <20170813174422.16197-1-hch@lst.de>
T24gU3VuLCAyMDE3LTA4LTEzIGF0IDE5OjQ0ICswMjAwLCBDaHJpc3RvcGggSGVsbHdpZyB3cm90
ZToNCj4gRGVmYXVsdGluZyB0byBzY3NpLW1xIGluIDQuMTMtcmMgaGFzIHNob3duIHZhcmlvdXMg
cmVncmVzc2lvbnMNCj4gb24gc2V0dXBzIHRoYXQgd2UgZGlkbid0IHByZXZpb3VzbHkgY29uc2lk
ZXIuICBGaXhlcyBmb3IgdGhlbSBhcmUNCj4gaW4gcHJvZ3Jlc3MsIGJ1dCB0b28gaW52YXNpdmUg
dG8gbWFrZSBpdCBpbiB0aGlzIGN5Y2xlLiAgU28gZm9yDQo+IG5vdyByZXZlcnQgdGhlIGNvbW1p
dCB0aGF0IGRlZmF1bHRzIHRvIGJsay1tcSBmb3IgU0NTSS4gIEZvciA0LjE0DQo+IHdlJ2xsIHBs
YW4gdG8gdHJ5IGFnYWluIHdpdGggdGhlc2UgZml4ZXMuDQoNClNob3VsZCBhIHBhdGNoIGZvciB2
NC4xNCBwZXJoYXBzIGJlIHF1ZXVlZCBub3c/IEFueXdheToNCg0KUmV2aWV3ZWQtYnk6IEJhcnQg
VmFuIEFzc2NoZSA8YmFydC52YW5hc3NjaGVAd2RjLmNvbT4NCg0K
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "hch@lst.de" <hch@lst.de>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] Revert "scsi: default to scsi-mq"
Date: Mon, 14 Aug 2017 15:21:06 +0000 [thread overview]
Message-ID: <1502724064.2333.5.camel@wdc.com> (raw)
In-Reply-To: <20170813174422.16197-1-hch@lst.de>
On Sun, 2017-08-13 at 19:44 +0200, Christoph Hellwig wrote:
> Defaulting to scsi-mq in 4.13-rc has shown various regressions
> on setups that we didn't previously consider. Fixes for them are
> in progress, but too invasive to make it in this cycle. So for
> now revert the commit that defaults to blk-mq for SCSI. For 4.14
> we'll plan to try again with these fixes.
Should a patch for v4.14 perhaps be queued now? Anyway:
Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com>
next prev parent reply other threads:[~2017-08-14 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 17:44 [PATCH] Revert "scsi: default to scsi-mq" Christoph Hellwig
2017-08-14 6:23 ` Hannes Reinecke
2017-08-14 15:21 ` Bart Van Assche [this message]
2017-08-14 15:21 ` Bart Van Assche
2017-08-16 11:13 ` Adrian Hunter
2017-08-14 15:50 ` Dave Kleikamp
2017-08-15 2:58 ` Martin K. Petersen
2017-08-16 5:53 ` [lkp-robot] [scsi] 39b54b0fd0: fileio.requests_per_sec 11.9% improvement kernel test robot
2017-08-16 5:53 ` kernel test robot
2017-08-16 5:53 ` kernel test robot
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=1502724064.2333.5.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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.