From: Adrian Hunter <adrian.hunter@intel.com>
To: Bough Chen <haibo.chen@nxp.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Shawn Lin <shawn.lin@rock-chips.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
Alex Lemberg <alex.lemberg@sandisk.com>,
Mateusz Nowak <mateusz.nowak@intel.com>,
Yuliy Izrailov <Yuliy.Izrailov@sandisk.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Dong Aisheng <dongas86@gmail.com>,
Das Asutosh <asutoshd@codeaurora.org>,
Zhangfei Gao <zhangfei.gao@gmail.com>,
Sahitya Tummala <stummala@codeaurora.org>,
Harjani Ritesh <riteshh@codeaurora.org>,
Venu Byravarasu <vbyravarasu@nvidia.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH V5 00/13] mmc: Add Command Queue support
Date: Fri, 18 Aug 2017 14:03:32 +0300 [thread overview]
Message-ID: <ac4d7a84-dbee-d789-e5d4-2191a201fcac@intel.com> (raw)
In-Reply-To: <AM4PR0401MB2324B4E9B0818CCC3D70113090830@AM4PR0401MB2324.eurprd04.prod.outlook.com>
On 17/08/17 10:45, Bough Chen wrote:
>
>> -----Original Message-----
>> From: linux-mmc-owner@vger.kernel.org [mailto:linux-mmc-
>> owner@vger.kernel.org] On Behalf Of Adrian Hunter
>> Sent: Thursday, August 10, 2017 8:08 PM
>> To: Ulf Hansson <ulf.hansson@linaro.org>
>> Cc: linux-mmc <linux-mmc@vger.kernel.org>; Bough Chen
>> <haibo.chen@nxp.com>; Alex Lemberg <alex.lemberg@sandisk.com>;
>> Mateusz Nowak <mateusz.nowak@intel.com>; Yuliy Izrailov
>> <Yuliy.Izrailov@sandisk.com>; Jaehoon Chung <jh80.chung@samsung.com>;
>> Dong Aisheng <dongas86@gmail.com>; Das Asutosh
>> <asutoshd@codeaurora.org>; Zhangfei Gao <zhangfei.gao@gmail.com>;
>> Sahitya Tummala <stummala@codeaurora.org>; Harjani Ritesh
>> <riteshh@codeaurora.org>; Venu Byravarasu <vbyravarasu@nvidia.com>;
>> Linus Walleij <linus.walleij@linaro.org>; Shawn Lin <shawn.lin@rock-chips.com>
>> Subject: [PATCH V5 00/13] mmc: Add Command Queue support
>>
>> Hi
>>
>> Here is V5 of the hardware command queue patches without the software
>> command queue patches.
>>
>> HW CMDQ offers 25% - 50% better random multi-threaded I/O. I see a slight 2%
>> drop in sequential read speed but no change to sequential write.
>>
>>
> Hi Adrian,
>
> I test the performance on the i.MX8. Here in my side, I use 'dd' to test the
> sequential read/write speed, see a slight 3% drop for both read and write.
>
> ---------------------------------------------
> | | read (KB/s)| write (KB/s) |
> ---------------------------------------------
> |CMDQ in HS400ES| 257 | 94.5 |
> ---------------------------------------------
> | HS400ES | 265 | 96.6 |
> ---------------------------------------------
>
> For random multi-threaded I/O, I use 'fio' to test, the test command:
> fio -filename=/mnt/test -direct=1 -iodepth 1 -thread -rw=randread - ioengine=psync -bs=4k -size=2G -numjobs=10 -runtime=60 -group_reporting - name=mytest
>
> I test 5 times, and get the average value.
> For CMDQ in HS400ES
> ----------------------------------------------------
> | block size | 4KB | 8KB | 16KB |
> ----------------------------------------------------
> | random read | 26340KB/s | 51844KB/s | 85738KB/s |
> ----------------------------------------------------
> | random write | 12691KB/s | 15879KB/s | 17535KB/s |
> ----------------------------------------------------
>
> HS400ES without CMDQ
> ----------------------------------------------------
> | block size | 4KB | 8KB | 16KB |
> ----------------------------------------------------
> | random read | 18585KB/s | 35041KB/s | 63880KB/s |
> ----------------------------------------------------
> | random write | 16465KB/s | 19210KB/s | 22672KB/s |
> ----------------------------------------------------
>
> For random write from the test, I find every test value differ greatly no matter enable CMDQ or not.
>
>>From the test, I see CMDQ random read speed increase 34%~48%, but for random write, the speed
> drop 17.4% ~ 33%.
>
> When you send software cmdq V5 patch, you give some explanation for the random write. But the
> average random write speed also drops a lot, I think it is now a good news, which need attention!
I tried your test and got quite variable results but did not see a drop:
CQ
4K 8K 16K
Random Write 10,374 KB/s 9,669 KB/s 10,712 KB/s
Non-CQ
4K 8K 16K
Random Write 9,898 KB/s 8,747 KB/s 9,098 KB/s
But given the variability of results I would not conclude CQ was faster.
I would suggest you run more tests and see if the trend continues.
next prev parent reply other threads:[~2017-08-18 11:10 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 12:08 [PATCH V5 00/13] mmc: Add Command Queue support Adrian Hunter
2017-08-10 12:08 ` [PATCH V5 01/13] mmc: core: Add mmc_retune_hold_now() Adrian Hunter
2017-08-20 11:26 ` Linus Walleij
2017-08-22 11:12 ` Ulf Hansson
2017-08-10 12:08 ` [PATCH V5 02/13] mmc: core: Add members to mmc_request and mmc_data for CQE's Adrian Hunter
2017-08-20 11:29 ` Linus Walleij
2017-08-21 9:26 ` Adrian Hunter
2017-08-22 11:12 ` Ulf Hansson
2017-08-10 12:08 ` [PATCH V5 03/13] mmc: host: Add CQE interface Adrian Hunter
2017-08-20 11:31 ` Linus Walleij
2017-08-22 11:13 ` Ulf Hansson
2017-08-23 6:54 ` Adrian Hunter
2017-08-23 12:48 ` Ulf Hansson
2017-08-24 6:53 ` Adrian Hunter
2017-08-24 9:24 ` Ulf Hansson
2017-08-10 12:08 ` [PATCH V5 04/13] mmc: core: Turn off CQE before sending commands Adrian Hunter
2017-08-20 11:32 ` Linus Walleij
2017-08-22 11:13 ` Ulf Hansson
2017-08-10 12:08 ` [PATCH V5 05/13] mmc: core: Add support for handling CQE requests Adrian Hunter
2017-08-20 11:39 ` Linus Walleij
2017-08-21 9:26 ` Adrian Hunter
2017-08-31 11:32 ` Linus Walleij
2017-08-22 8:06 ` Ulf Hansson
2017-08-10 12:08 ` [PATCH V5 06/13] mmc: core: Remove unused MMC_CAP2_PACKED_CMD Adrian Hunter
2017-08-20 11:33 ` Linus Walleij
2017-08-22 11:12 ` Ulf Hansson
2017-08-10 12:08 ` [PATCH V5 07/13] mmc: mmc: Enable Command Queuing Adrian Hunter
2017-08-20 11:33 ` Linus Walleij
2017-08-10 12:08 ` [PATCH V5 08/13] mmc: mmc: Enable CQE's Adrian Hunter
2017-08-20 11:41 ` Linus Walleij
2017-08-10 12:08 ` [PATCH V5 09/13] mmc: block: Use local variables in mmc_blk_data_prep() Adrian Hunter
2017-08-20 11:43 ` Linus Walleij
2017-08-21 9:27 ` Adrian Hunter
2017-08-10 12:08 ` [PATCH V5 10/13] mmc: block: Prepare CQE data Adrian Hunter
2017-08-10 12:08 ` [PATCH V5 11/13] mmc: block: Add CQE support Adrian Hunter
2017-08-20 12:13 ` Linus Walleij
2017-08-21 9:27 ` Adrian Hunter
2017-08-31 10:05 ` Linus Walleij
2017-08-31 10:25 ` Christoph Hellwig
2017-08-31 10:23 ` Christoph Hellwig
2017-08-31 12:00 ` Adrian Hunter
2017-08-10 12:08 ` [PATCH V5 12/13] mmc: cqhci: support for command queue enabled host Adrian Hunter
2017-08-10 12:08 ` [PATCH V5 13/13] mmc: sdhci-pci: Add CQHCI support for Intel GLK Adrian Hunter
2017-08-11 10:33 ` [PATCH V5 00/13] mmc: Add Command Queue support Bough Chen
2017-08-17 7:45 ` Bough Chen
2017-08-17 8:56 ` Shawn Lin
2017-08-18 11:03 ` Adrian Hunter [this message]
2017-08-18 11:06 ` Adrian Hunter
2017-08-22 11:22 ` Ulf Hansson
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=ac4d7a84-dbee-d789-e5d4-2191a201fcac@intel.com \
--to=adrian.hunter@intel.com \
--cc=Yuliy.Izrailov@sandisk.com \
--cc=alex.lemberg@sandisk.com \
--cc=asutoshd@codeaurora.org \
--cc=dongas86@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=jh80.chung@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mateusz.nowak@intel.com \
--cc=riteshh@codeaurora.org \
--cc=shawn.lin@rock-chips.com \
--cc=stummala@codeaurora.org \
--cc=ulf.hansson@linaro.org \
--cc=vbyravarasu@nvidia.com \
--cc=zhangfei.gao@gmail.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