From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bedivere.hansenpartnership.com ([66.63.167.143]:40598 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752915AbdHKOZx (ORCPT ); Fri, 11 Aug 2017 10:25:53 -0400 Message-ID: <1502461550.2647.4.camel@HansenPartnership.com> Subject: Re: [PATCH V2 00/20] blk-mq-sched: improve SCSI-MQ performance From: James Bottomley To: Christoph Hellwig , Ming Lei Cc: Jens Axboe , linux-block@vger.kernel.org, Bart Van Assche , Laurence Oberman , "Martin K. Petersen" , linux-scsi@vger.kernel.org Date: Fri, 11 Aug 2017 07:25:50 -0700 In-Reply-To: <20170811081135.GA4260@infradead.org> References: <20170805065705.12989-1-ming.lei@redhat.com> <20170811081135.GA4260@infradead.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-block-owner@vger.kernel.org List-Id: linux-block@vger.kernel.org On Fri, 2017-08-11 at 01:11 -0700, Christoph Hellwig wrote: > [+ Martin and linux-scsi] > > Given that we need this big pile and a few bfq fixes to avoid > major regressesions I'm tempted to revert the default to scsi-mq > for 4.14, but bring it back a little later for 4.15. > > What do you think?  Maybe for 4.15 we could also do it through the > block tree where all the fixes will be queued. Given the severe workload regressions Mel reported, I think that's wise. I also think we wouldn't have found all these problems if it hadn't been the default, so the original patch was the best way of trying to find out if we were ready for the switch and forcing all the issues out. Thanks, James