From: Christoph Hellwig <hch@infradead.org>
To: Shaohua Li <shli@fb.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Kernel-team@fb.com, axboe@fb.com
Subject: Re: [PATCH V2 2/2] blk-mq: immediately dispatch big size request
Date: Thu, 3 Nov 2016 17:09:54 -0700 [thread overview]
Message-ID: <20161104000954.GA10266@infradead.org> (raw)
In-Reply-To: <6297c9a39cf21c94c65d5a9b3a19e54ba5b8b573.1478217671.git.shli@fb.com>
On Thu, Nov 03, 2016 at 05:03:54PM -0700, Shaohua Li wrote:
> This is corresponding part for blk-mq. Disk with multiple hardware
> queues doesn't need this as we only hold 1 request at most.
Any reason you only do this for the SQ and not the MQ case?
next prev parent reply other threads:[~2016-11-04 0:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 0:03 [PATCH V2 1/2] block: immediately dispatch big size request Shaohua Li
2016-11-04 0:03 ` [PATCH V2 2/2] blk-mq: " Shaohua Li
2016-11-04 0:09 ` Christoph Hellwig [this message]
2016-11-04 0:13 ` Shaohua Li
2016-11-04 4:00 ` Jens Axboe
2016-11-04 14:46 ` Christoph Hellwig
2016-11-04 15:29 ` Jens Axboe
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=20161104000954.GA10266@infradead.org \
--to=hch@infradead.org \
--cc=Kernel-team@fb.com \
--cc=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shli@fb.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