From: Tom Nguyen <tom81094@gmail.com>
To: Oleksandr Natalenko <oleksandr@natalenko.name>, ming.lei@redhat.com
Cc: linux-block@vger.kernel.org, Jens Axboe <axboe@fb.com>
Subject: Re: [PATCH V4 00/14] blk-mq-sched: improve SCSI-MQ performance
Date: Thu, 7 Sep 2017 04:22:42 +0700 [thread overview]
Message-ID: <79aa95f8-08cf-0109-7755-f50d26a3dfea@gmail.com> (raw)
In-Reply-To: <4920915.asy8ac7Ink@natalenko.name>
Likewise with no problems on my work laptop with 4 days uptime.
Tested-by: Tom Nguyen <tom81094@gmail.com>
On 09/07/2017 04:09 AM, Oleksandr Natalenko wrote:
> Feel free to add:
>
> Tested-by: Oleksandr Natalenko <oleksandr@natalenko.name>
>
> since I'm running this on 4 machines without issues.
>
>> Hi Jens,
>>
>> Ping...
next prev parent reply other threads:[~2017-09-06 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 21:09 [PATCH V4 00/14] blk-mq-sched: improve SCSI-MQ performance Oleksandr Natalenko
2017-09-06 21:22 ` Tom Nguyen [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-02 15:17 Ming Lei
2017-09-04 9:12 ` Paolo Valente
2017-09-05 1:39 ` Ming Lei
2017-09-06 15:27 ` Ming Lei
2017-09-19 19:25 ` Omar Sandoval
2017-09-20 3:18 ` Ming Lei
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=79aa95f8-08cf-0109-7755-f50d26a3dfea@gmail.com \
--to=tom81094@gmail.com \
--cc=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=oleksandr@natalenko.name \
/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;
as well as URLs for NNTP newsgroup(s).