From: Jens Axboe <axboe@kernel.dk>
To: Joseph Qi <jiangqi903@gmail.com>
Cc: linux-block <linux-block@vger.kernel.org>,
Shaohua Li <shli@fb.com>,
qijiang.qj@alibaba-inc.com
Subject: Re: [PATCH v3 RESEND 1/2] blk-throttle: track read and write request individually
Date: Thu, 23 Nov 2017 22:13:02 -0700 [thread overview]
Message-ID: <ea069c52-1080-3ff7-1e52-66a9fbea79c1@kernel.dk> (raw)
In-Reply-To: <ee08d6bf-dea8-2b80-b20d-1229409f3542@gmail.com>
On 11/23/2017 06:31 PM, Joseph Qi wrote:
> Hi Jens,
> Could you please give your advice for the two patches or pick them up if
> you think they are good?
It looks OK to me, but my preference would be to push this until
4.16.
--
Jens Axboe
next prev parent reply other threads:[~2017-11-24 5:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 1:38 [PATCH v3 RESEND 1/2] blk-throttle: track read and write request individually Joseph Qi
2017-11-24 1:31 ` Joseph Qi
2017-11-24 5:13 ` Jens Axboe [this message]
2018-01-08 12:05 ` Joseph Qi
2018-01-19 2:11 ` Joseph Qi
2018-01-19 2:52 ` Jens Axboe
2018-01-19 2:54 ` Joseph Qi
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=ea069c52-1080-3ff7-1e52-66a9fbea79c1@kernel.dk \
--to=axboe@kernel.dk \
--cc=jiangqi903@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=qijiang.qj@alibaba-inc.com \
--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