All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Michael Kelley <mikelley@microsoft.com>
Cc: KY Srinivasan <kys@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	Long Li <longli@microsoft.com>,
	"James.Bottomley@hansenpartnership.com"
	<James.Bottomley@hansenpartnership.com>,
	"emilne@redhat.com" <emilne@redhat.com>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 1/1] scsi: storvsc: Always use blk-mq
Date: Wed, 19 Dec 2018 21:51:04 -0500	[thread overview]
Message-ID: <yq14lb8gbc7.fsf@oracle.com> (raw)
In-Reply-To: <1545243282-10573-1-git-send-email-mikelley@microsoft.com> (Michael Kelley's message of "Wed, 19 Dec 2018 18:40:49 +0000")


Michael,

> With high IOPS storage being increasingly prevalent for guests
> on Hyper-V and in Azure, make blk-mq the default so that the
> full performance of the storage can be realized without having
> to tweak other configuration settings.

The legacy I/O path will be gone in 4.21 so this patch isn't needed.

-- 
Martin K. Petersen	Oracle Linux Engineering

WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Michael Kelley <mikelley@microsoft.com>
Cc: KY Srinivasan <kys@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	"martin.petersen\@oracle.com" <martin.petersen@oracle.com>,
	Long Li <longli@microsoft.com>,
	"James.Bottomley\@hansenpartnership.com" 
	<James.Bottomley@hansenpartnership.com>,
	"emilne\@redhat.com" <emilne@redhat.com>,
	"devel\@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 1/1] scsi: storvsc: Always use blk-mq
Date: Wed, 19 Dec 2018 21:51:04 -0500	[thread overview]
Message-ID: <yq14lb8gbc7.fsf@oracle.com> (raw)
In-Reply-To: <1545243282-10573-1-git-send-email-mikelley@microsoft.com> (Michael Kelley's message of "Wed, 19 Dec 2018 18:40:49 +0000")


Michael,

> With high IOPS storage being increasingly prevalent for guests
> on Hyper-V and in Azure, make blk-mq the default so that the
> full performance of the storage can be realized without having
> to tweak other configuration settings.

The legacy I/O path will be gone in 4.21 so this patch isn't needed.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2018-12-20  2:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19 18:40 [PATCH 1/1] scsi: storvsc: Always use blk-mq Michael Kelley
2018-12-20  2:51 ` Martin K. Petersen [this message]
2018-12-20  2:51   ` Martin K. Petersen

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=yq14lb8gbc7.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=devel@linuxdriverproject.org \
    --cc=emilne@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=longli@microsoft.com \
    --cc=mikelley@microsoft.com \
    --cc=sthemmin@microsoft.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.