public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-block@vger.kernel.org, Marco Patalano <mpatalan@redhat.com>,
	"Ewan D. Milne" <emilne@redhat.com>
Subject: Re: [PATCH] blk-mq: update nr_requests when switching to 'none' scheduler
Date: Sat, 2 Jun 2018 14:08:15 -0600	[thread overview]
Message-ID: <12c6487b-9bb6-d208-35a3-e8fadbd2acf2@kernel.dk> (raw)
In-Reply-To: <20180602071809.4277-1-ming.lei@redhat.com>

On 6/2/18 1:18 AM, Ming Lei wrote:
> Now we setup q->nr_requests when switching to one new scheduler,
> but not do it for 'none', then q->nr_requests may not be correct
> for 'none'.
> 
> This patch fixes this issue by always updating 'nr_requests' when
> switching to 'none'.

Looks fine, applied.

-- 
Jens Axboe

      reply	other threads:[~2018-06-02 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-02  7:18 [PATCH] blk-mq: update nr_requests when switching to 'none' scheduler Ming Lei
2018-06-02 20:08 ` Jens Axboe [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=12c6487b-9bb6-d208-35a3-e8fadbd2acf2@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=emilne@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=mpatalan@redhat.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