[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linaro-flashbench-results
Subject:    [Flashbench] Samsung Memory MB-MP64D 64GB EVO MicroSDXC UHS-I Grade Class 10 MicroSDXC
From:       Martin Steigerwald <Martin () lichtvoll ! de>
Date:       2014-08-31 10:02:26
Message-ID: 3378578.rz0IJHdAGc () merkaba
[Download RAW message or body]

Hello!

Three runs of my flashreport script[1] which uses flashbench as well as the
open au benchmarks it suggested but additionally with report preferred erase
block size as well.

It seems pretty clear to me from the factory partitioning and the benchmark
results that the device prefers an erase block size of large 16 MiB. But
even with the reported default erase block size it seems to work quite
well. Do you agree with this interpretation?

I am not sure about the open au numbers as benchmark results do not vary
much. It appears to me that it seems to slightly prefer lower open au
numbers like 3 or 5 seem to be slightly preferable. For the intended use in
Sandisk e260v1 with Rockbox open au numbers would not matter anyway as
they are only setable with F2FS I think. The card indeed does work in it,
reformatted to FAT32 (from ExFAT) and with partition type 0xc. I re-used
the manufacturer partitioning.

The included SD adapter from Samsung seems to have contact issues with
SD card slot in ThinkPad T520. An Intenso I already had here one has no
such issues. Except from kern.log:

Aug 31 10:37:04 merkaba kernel: [215894.957529] mmc0: card 0001 removed
Aug 31 10:37:06 merkaba kernel: [215896.457997] mmc0: new high speed SDXC card at \
                address 0001
Aug 31 10:37:06 merkaba kernel: [215896.458528] mmcblk0: mmc0:0001 00000 58.5 GiB 
Aug 31 10:37:06 merkaba kernel: [215896.460570] mmc0: Got data interrupt 0x00200000 \
                even though no data operation was in progress.
Aug 31 10:37:06 merkaba kernel: [215896.460717] mmcblk0: error -110 sending status \
                command, retrying
Aug 31 10:37:06 merkaba kernel: [215896.460768] mmcblk0: error -110 sending status \
                command, retrying
Aug 31 10:37:06 merkaba kernel: [215896.460820] mmcblk0: error -110 sending status \
                command, aborting
Aug 31 10:37:06 merkaba kernel: [215896.460833] blk_update_request: 8 callbacks \
                suppressed
Aug 31 10:37:06 merkaba kernel: [215896.460837] end_request: I/O error, dev mmcblk0, \
                sector 0
Aug 31 10:37:06 merkaba kernel: [215896.460842] quiet_error: 8 callbacks suppressed
Aug 31 10:37:06 merkaba kernel: [215896.460846] Buffer I/O error on device mmcblk0, \
                logical block 0
Aug 31 10:37:06 merkaba kernel: [215896.470999] mmc0: Controller never released \
                inhibit bit(s).
Aug 31 10:37:06 merkaba kernel: [215896.471207] mmcblk0: error -5 sending status \
                command, retrying
Aug 31 10:37:06 merkaba kernel: [215896.471272] mmcblk0: error -110 sending status \
                command, retrying
Aug 31 10:37:06 merkaba kernel: [215896.471324] mmcblk0: error -110 sending status \
                command, aborting
Aug 31 10:37:06 merkaba kernel: [215896.471337] end_request: I/O error, dev mmcblk0, \
                sector 0
Aug 31 10:37:06 merkaba kernel: [215896.471343] Buffer I/O error on device mmcblk0, \
                logical block 0
Aug 31 10:37:06 merkaba kernel: [215896.481525] mmc0: Controller never released \
                inhibit bit(s).
Aug 31 10:37:06 merkaba kernel: [215896.481678] mmcblk0: error -5 sending status \
                command, retrying
Aug 31 10:37:06 merkaba kernel: [215896.481742] mmcblk0: error -110 sending status \
                command, retrying
Aug 31 10:37:06 merkaba kernel: [215896.481796] mmcblk0: error -110 sending status \
                command, aborting
Aug 31 10:37:06 merkaba kernel: [215896.481809] end_request: I/O error, dev mmcblk0, \
sector 0

If I really insert it slowly and press it till the arrester it seems to work,
but I rather prefer the Intenso adapter for now.


Benchmark results follow:

===== Benchmarks in ThinkPad T520 internal SD card reader =====
merkaba:~> lspci -nn | grep MMC  
0d:00.0 System peripheral [0880]: Ricoh Co Ltd MMC/SD Host Controller [1180:e822] \
(rev 08)

merkaba:~> tail -fn0 /var/log/kern.log
Aug 31 10:34:58 merkaba kernel: [215768.587240] mmc0: card 0001 removed
Aug 31 10:35:50 merkaba kernel: [215820.887063] mmc0: new high speed SDXC card at \
                address 0001
Aug 31 10:35:50 merkaba kernel: [215820.887507] mmcblk0: mmc0:0001 00000 58.5 GiB 
Aug 31 10:35:50 merkaba kernel: [215820.888892]  mmcblk0: p1

Device has 62881005568 bytes:

martin@merkaba:~> factor 62881005568
62881005568: 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 937


=== First run of flashreport script ===
martin@merkaba:~/[…]/flashbench> ./flashreport /dev/mmcblk0 

===> MMC card detected with erase block size of 524288 bytes <===
==> find /sys/block/mmcblk0/device/ -maxdepth 1 -type f | xargs head <==

==> /sys/block/mmcblk0/device/cid <==
1b534d303030303010f216606c00e300

==> /sys/block/mmcblk0/device/csd <==
400e00325b590001d47f7f800a404000

==> /sys/block/mmcblk0/device/scr <==
02c5800300000000

==> /sys/block/mmcblk0/device/date <==
03/2014

==> /sys/block/mmcblk0/device/name <==
00000

==> /sys/block/mmcblk0/device/type <==
SD

==> /sys/block/mmcblk0/device/preferred_erase_size <==
16777216

==> /sys/block/mmcblk0/device/fwrev <==
0x0

==> /sys/block/mmcblk0/device/hwrev <==
0x1

==> /sys/block/mmcblk0/device/oemid <==
0x534d

==> /sys/block/mmcblk0/device/manfid <==
0x00001b

==> /sys/block/mmcblk0/device/serial <==
0xf216606c

==> /sys/block/mmcblk0/device/uevent <==
DRIVER=mmcblk
MMC_TYPE=SD
MMC_NAME=00000
MODALIAS=mmc:block

==> /sys/block/mmcblk0/device/erase_size <==
512

==> fdisk -lu <==
[sudo] password for martin: 

Disk /dev/mmcblk0: 58.6 GiB, 62881005568 bytes, 122814464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device         Boot Start       End   Sectors  Size Id Type
/dev/mmcblk0p1      32768 122814463 122781696 58.6G  7 HPFS/NTFS/exFAT

==> sfdisk -d <==
# partition table of /dev/mmcblk0
unit: sectors

/dev/mmcblk0p1 : start=    32768, size=122781696, Id= 7
/dev/mmcblk0p2 : start=        0, size=        0, Id= 0
/dev/mmcblk0p3 : start=        0, size=        0, Id= 0
/dev/mmcblk0p4 : start=        0, size=        0, Id= 0

===> Partition details <===

==> sudo file -sk /dev/mmcblk0 <==
/dev/mmcblk0: DOS/MBR boot sector; partition 1 : ID=0x7, start-CHS (0x2,10,9), \
end-CHS (0x3ff,254,63), startsector 32768, 122781696 sectors, extended partition \
table (last)\011

==> sudo file -sk /dev/mmcblk0p1 <==
/dev/mmcblk0p1: DOS/MBR boot sector

==> head -c20M | hexdump -C<==
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001b0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 0a  |................|
000001c0  09 02 07 fe ff ff 00 80  00 00 00 80 51 07 00 00  |............Q...|
000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01000000  eb 76 90 45 58 46 41 54  20 20 20 00 00 00 00 00  |.v.EXFAT   .....|
01000010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01000040  00 80 00 00 00 00 00 00  00 80 51 07 00 00 00 00  |..........Q.....|
01000050  00 40 00 00 00 40 00 00  00 80 00 00 00 51 07 00  |.@...@.......Q..|
01000060  04 00 00 00 00 00 00 00  00 01 00 00 09 08 01 80  |................|
01000070  00 00 00 00 00 00 00 00  f4 f4 f4 f4 f4 f4 f4 f4  |................|
01000080  f4 f4 f4 f4 f4 f4 f4 f4  f4 f4 f4 f4 f4 f4 f4 f4  |................|
*
010001f0  f4 f4 f4 f4 f4 f4 f4 f4  f4 f4 f4 f4 f4 f4 55 aa  |..............U.|
01000200  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
010003f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01000400  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
010005f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01000600  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
010007f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01000800  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
010009f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01000a00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01000bf0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01000c00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01000df0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01000e00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01000ff0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01001000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
010011f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01001200  46 7e 0c 0a 99 33 21 40  90 c8 fa 6d 38 9c 4b a2  |F~...3!@...m8.K.|
01001210  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01001600  d3 f8 4a 22 d3 f8 4a 22  d3 f8 4a 22 d3 f8 4a 22  |..J"..J"..J"..J"|
*
01001800  eb 76 90 45 58 46 41 54  20 20 20 00 00 00 00 00  |.v.EXFAT   .....|
01001810  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01001840  00 80 00 00 00 00 00 00  00 80 51 07 00 00 00 00  |..........Q.....|
01001850  00 40 00 00 00 40 00 00  00 80 00 00 00 51 07 00  |.@...@.......Q..|
01001860  04 00 00 00 00 00 00 00  00 01 00 00 09 08 01 80  |................|
01001870  00 00 00 00 00 00 00 00  f4 f4 f4 f4 f4 f4 f4 f4  |................|
01001880  f4 f4 f4 f4 f4 f4 f4 f4  f4 f4 f4 f4 f4 f4 f4 f4  |................|
*
010019f0  f4 f4 f4 f4 f4 f4 f4 f4  f4 f4 f4 f4 f4 f4 55 aa  |..............U.|
01001a00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01001bf0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01001c00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01001df0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01001e00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01001ff0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01002000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
010021f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01002200  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
010023f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01002400  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
010025f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01002600  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
010027f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01002800  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
010029f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
01002a00  46 7e 0c 0a 99 33 21 40  90 c8 fa 6d 38 9c 4b a2  |F~...3!@...m8.K.|
01002a10  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01002e00  d3 f8 4a 22 d3 f8 4a 22  d3 f8 4a 22 d3 f8 4a 22  |..J"..J"..J"..J"|
*
01003000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
01400000


===> Trying to find erase block size by read tests <===

==> sudo flashbench -a --count=100 --blocksize=1024 /dev/mmcblk0 <==
align 17179869184       pre 439 µs       on 579 µs        post 277 µs      diff 221 \
µs align 8589934592        pre 440 µs       on 580 µs        post 277 µs      diff \
221 µs align 4294967296        pre 437 µs       on 578 µs        post 274 µs      \
diff 223 µs align 2147483648        pre 440 µs       on 580 µs        post 278 µs     \
diff 221 µs align 1073741824        pre 440 µs       on 579 µs        post 277 µs     \
diff 221 µs align 536870912 pre 440 µs       on 579 µs        post 277 µs      diff \
221 µs align 268435456 pre 439 µs       on 578 µs        post 277 µs      diff 221 µs
align 134217728 pre 446 µs       on 588 µs        post 286 µs      diff 222 µs
align 67108864  pre 444 µs       on 584 µs        post 282 µs      diff 221 µs
align 33554432  pre 414 µs       on 551 µs        post 275 µs      diff 207 µs
align 16777216  pre 422 µs       on 562 µs        post 287 µs      diff 207 µs
align 8388608   pre 280 µs       on 404 µs        post 281 µs      diff 124 µs
align 4194304   pre 284 µs       on 407 µs        post 279 µs      diff 126 µs
align 2097152   pre 291 µs       on 415 µs        post 291 µs      diff 124 µs
align 1048576   pre 295 µs       on 420 µs        post 291 µs      diff 127 µs
align 524288    pre 293 µs       on 417 µs        post 293 µs      diff 124 µs
align 262144    pre 287 µs       on 411 µs        post 282 µs      diff 127 µs
align 131072    pre 287 µs       on 411 µs        post 283 µs      diff 126 µs
align 65536     pre 287 µs       on 411 µs        post 291 µs      diff 122 µs
align 32768     pre 274 µs       on 397 µs        post 273 µs      diff 123 µs
align 16384     pre 274 µs       on 398 µs        post 274 µs      diff 124 µs
align 8192      pre 273 µs       on 273 µs        post 273 µs      diff 348ns
align 4096      pre 281 µs       on 281 µs        post 281 µs      diff 136ns
align 2048      pre 267 µs       on 267 µs        post 266 µs      diff 557ns

(See README for an explaination on how to interpret the values.)

Medium is a memory card which reports 524288 bytes as erase block size
and 16777216 bytes as preferred erase size.

===> Suggestions for further benchmarking <===

Further tests can show the number of open erase blocks the medium
can support.

BEWARE: These tests write onto the device! Make a backup first!

Further tests could look as follows:
flashbench --open-au --open-au-nr=3 --erasesize=524288 --blocksize=1024 /dev/mmcblk0 \
--offset=$[24*1024*1024] flashbench --open-au --open-au-nr=5 --erasesize=524288 \
--blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] flashbench --open-au \
--open-au-nr=7 --erasesize=524288 --blocksize=1024 /dev/mmcblk0 \
--offset=$[24*1024*1024] flashbench --open-au --open-au-nr=13 --erasesize=524288 \
--blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024]

(Consult the README for further suggestions.)



=== Second run of flashreport script ===
martin@merkaba:~/…/flashbench> ./flashreport /dev/mmcblk0

===> MMC card detected with erase block size of 524288 bytes <===
[…]
===> Trying to find erase block size by read tests <===

==> sudo flashbench -a --count=100 --blocksize=1024 /dev/mmcblk0 <==
align 17179869184       pre 463 µs       on 602 µs        post 301 µs      diff 221 \
µs align 8589934592        pre 462 µs       on 601 µs        post 299 µs      diff \
221 µs align 4294967296        pre 448 µs       on 588 µs        post 285 µs      \
diff 221 µs align 2147483648        pre 467 µs       on 608 µs        post 304 µs     \
diff 223 µs align 1073741824        pre 456 µs       on 595 µs        post 293 µs     \
diff 220 µs align 536870912 pre 456 µs       on 596 µs        post 292 µs      diff \
221 µs align 268435456 pre 451 µs       on 593 µs        post 286 µs      diff 224 µs
align 134217728 pre 455 µs       on 594 µs        post 288 µs      diff 222 µs
align 67108864  pre 445 µs       on 585 µs        post 284 µs      diff 221 µs
align 33554432  pre 435 µs       on 573 µs        post 293 µs      diff 208 µs
align 16777216  pre 422 µs       on 560 µs        post 284 µs      diff 207 µs
align 8388608   pre 285 µs       on 409 µs        post 285 µs      diff 124 µs
align 4194304   pre 291 µs       on 416 µs        post 287 µs      diff 127 µs
align 2097152   pre 294 µs       on 417 µs        post 293 µs      diff 124 µs
align 1048576   pre 292 µs       on 416 µs        post 288 µs      diff 126 µs
align 524288    pre 287 µs       on 409 µs        post 285 µs      diff 124 µs
align 262144    pre 283 µs       on 407 µs        post 278 µs      diff 126 µs
align 131072    pre 285 µs       on 409 µs        post 280 µs      diff 126 µs
align 65536     pre 283 µs       on 407 µs        post 287 µs      diff 122 µs
align 32768     pre 289 µs       on 411 µs        post 288 µs      diff 123 µs
align 16384     pre 278 µs       on 402 µs        post 278 µs      diff 124 µs
align 8192      pre 282 µs       on 281 µs        post 281 µs      diff -523ns
align 4096      pre 283 µs       on 283 µs        post 283 µs      diff 131ns
align 2048      pre 286 µs       on 285 µs        post 285 µs      diff -817ns

(See README for an explaination on how to interpret the values.)

Medium is a memory card which reports 524288 bytes as erase block size
and 16777216 bytes as preferred erase size.

[…]

=== Third run of flashreport script ===
martin@merkaba:~/…/flashbench> ./flashreport /dev/mmcblk0
[…]
===> Trying to find erase block size by read tests <===

==> sudo flashbench -a --count=100 --blocksize=1024 /dev/mmcblk0 <==
align 17179869184       pre 457 µs       on 597 µs        post 295 µs      diff 221 \
µs align 8589934592        pre 453 µs       on 593 µs        post 289 µs      diff \
222 µs align 4294967296        pre 463 µs       on 602 µs        post 299 µs      \
diff 221 µs align 2147483648        pre 447 µs       on 586 µs        post 284 µs     \
diff 221 µs align 1073741824        pre 450 µs       on 590 µs        post 286 µs     \
diff 222 µs align 536870912 pre 451 µs       on 590 µs        post 286 µs      diff \
221 µs align 268435456 pre 446 µs       on 585 µs        post 283 µs      diff 221 µs
align 134217728 pre 449 µs       on 589 µs        post 285 µs      diff 222 µs
align 67108864  pre 453 µs       on 594 µs        post 291 µs      diff 222 µs
align 33554432  pre 420 µs       on 557 µs        post 280 µs      diff 206 µs
align 16777216  pre 423 µs       on 560 µs        post 284 µs      diff 207 µs
align 8388608   pre 284 µs       on 408 µs        post 283 µs      diff 124 µs
align 4194304   pre 291 µs       on 415 µs        post 286 µs      diff 127 µs
align 2097152   pre 286 µs       on 409 µs        post 285 µs      diff 124 µs
align 1048576   pre 290 µs       on 414 µs        post 286 µs      diff 126 µs
align 524288    pre 293 µs       on 419 µs        post 293 µs      diff 126 µs
align 262144    pre 287 µs       on 412 µs        post 283 µs      diff 127 µs
align 131072    pre 285 µs       on 408 µs        post 279 µs      diff 126 µs
align 65536     pre 301 µs       on 426 µs        post 305 µs      diff 123 µs
align 32768     pre 283 µs       on 408 µs        post 283 µs      diff 124 µs
align 16384     pre 279 µs       on 403 µs        post 278 µs      diff 124 µs
align 8192      pre 279 µs       on 279 µs        post 279 µs      diff 300ns
align 4096      pre 280 µs       on 279 µs        post 279 µs      diff 133ns
align 2048      pre 279 µs       on 279 µs        post 279 µs      diff 52ns

(See README for an explaination on how to interpret the values.)

Medium is a memory card which reports 524288 bytes as erase block size
and 16777216 bytes as preferred erase size.
[…]



Some open au write benchmarks. It seems to me: Either the Samsung rating of
48 MB/s is highly overrated or the cardreader is not UHS-1 capable.


martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=3 \
--erasesize=524288 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 512KiB  \
12.5M/s  256KiB  14M/s   
128KiB  13.8M/s 
64KiB   14.2M/s 
32KiB   14.6M/s 
16KiB   10.5M/s 
8KiB    6.45M/s 
4KiB    3.54M/s 
2KiB    1.87M/s 
1KiB    922K/s  
martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=5 \
--erasesize=524288 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 512KiB  \
14M/s    256KiB  14.3M/s 
128KiB  12.6M/s 
64KiB   13.3M/s 
32KiB   12.7M/s 
16KiB   11.6M/s 
8KiB    7.11M/s 
4KiB    3.8M/s  
2KiB    1.93M/s 
1KiB    973K/s  
martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=7 \
--erasesize=524288 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 512KiB  \
13.6M/s  256KiB  14M/s   
128KiB  14.2M/s 
64KiB   13.3M/s 
32KiB   12.8M/s 
16KiB   11.5M/s 
8KiB    6.68M/s 
4KiB    3.73M/s 
2KiB    1.93M/s 
1KiB    962K/s  
martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=13 \
--erasesize=524288 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 512KiB  \
13.5M/s  256KiB  14M/s   
128KiB  13.9M/s 
64KiB   12.9M/s 
32KiB   12.4M/s 
16KiB   10.7M/s 
8KiB    6.79M/s 
4KiB    3.76M/s 
2KiB    1.86M/s 
1KiB    957K/s 



martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=3 \
--erasesize=16777216 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024]  16MiB   \
14.1M/s  8MiB    13.6M/s 
4MiB    13.5M/s 
2MiB    13.6M/s 
1MiB    13.4M/s 
512KiB  13.3M/s 
256KiB  13.1M/s 
128KiB  12.9M/s 
64KiB   12.9M/s 
32KiB   13.1M/s 
16KiB   10.4M/s 
8KiB    6.37M/s 
4KiB    3.6M/s  
2KiB    1.83M/s 
1KiB    948K/s  

martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=5 \
--erasesize=16777216 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 16MiB   \
13.8M/s  8MiB    13.6M/s 
4MiB    13.5M/s 
2MiB    13.7M/s 
1MiB    13.5M/s 
512KiB  13.3M/s 
256KiB  13.4M/s 
128KiB  13M/s   
64KiB   12.7M/s 
32KiB   12.2M/s 
16KiB   9.88M/s 
8KiB    6.14M/s 
4KiB    3.54M/s 
2KiB    1.76M/s 
1KiB    897K/s 

martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=7 \
--erasesize=16777216 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 16MiB   \
13.7M/s  8MiB    13.6M/s 
4MiB    13.6M/s 
2MiB    13.4M/s 
1MiB    13.4M/s 
512KiB  13.1M/s 
256KiB  13.3M/s 
128KiB  13M/s   
64KiB   12.8M/s 
32KiB   12.2M/s 
16KiB   9.91M/s 
8KiB    6.18M/s 
4KiB    3.54M/s 
2KiB    1.76M/s 
1KiB    914K/s

martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=13 \
--erasesize=16777216 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 16MiB   \
13.9M/s  8MiB    13.6M/s 
4MiB    13.8M/s 
2MiB    13.4M/s 
1MiB    13.5M/s 
512KiB  13.2M/s 
256KiB  12.8M/s 
128KiB  12M/s   
64KiB   11M/s   
32KiB   9.37M/s 
16KiB   6.45M/s 
8KiB    3.07M/s 
4KiB    1.6M/s  
2KiB    797K/s  
1KiB    408K/s 


===== Benchmarks in digisol 2.0 Multi Card Reader 5.1 =====
Seems to be a Transcend reader:

merkaba:~> lsusb | grep Transcend
Bus 002 Device 007: ID 1307:0330 Transcend Information, Inc. 63-in-1 Multi-Card \
Reader/Writer

merkaba:~> tail -fn0 /var/log/kern.log
Aug 31 10:51:49 merkaba kernel: [216779.647323] usb 2-1.1: new high-speed USB device \
                number 7 using ehci-pci
Aug 31 10:51:49 merkaba kernel: [216779.930706] usb 2-1.1: New USB device found, \
                idVendor=1307, idProduct=0330
Aug 31 10:51:49 merkaba kernel: [216779.930721] usb 2-1.1: New USB device strings: \
                Mfr=1, Product=2, SerialNumber=3
Aug 31 10:51:49 merkaba kernel: [216779.930728] usb 2-1.1: Product: Mass Storage \
                Device
Aug 31 10:51:49 merkaba kernel: [216779.930734] usb 2-1.1: Manufacturer: Generic
Aug 31 10:51:49 merkaba kernel: [216779.930739] usb 2-1.1: SerialNumber: \
                00000000000006
Aug 31 10:51:49 merkaba kernel: [216779.931712] usb-storage 2-1.1:1.0: USB Mass \
                Storage device detected
Aug 31 10:51:49 merkaba kernel: [216779.931996] scsi host13: usb-storage 2-1.1:1.0
Aug 31 10:51:50 merkaba kernel: [216780.935185] scsi 13:0:0:0: Direct-Access     \
                Generic  USB  CF Reader   0.00 PQ: 0 ANSI: 2
Aug 31 10:51:50 merkaba kernel: [216780.935856] scsi 13:0:0:1: Direct-Access     \
                Generic  USB  SD Reader   0.00 PQ: 0 ANSI: 2
Aug 31 10:51:50 merkaba kernel: [216780.936529] scsi 13:0:0:2: Direct-Access     \
                Generic  Mini SD Reader   0.00 PQ: 0 ANSI: 2
Aug 31 10:51:50 merkaba kernel: [216780.937054] scsi 13:0:0:3: Direct-Access     \
                Generic  USB  MS Reader   0.00 PQ: 0 ANSI: 2
Aug 31 10:51:50 merkaba kernel: [216780.937556] scsi 13:0:0:4: Direct-Access     \
                Generic  USB  SM Reader   0.00 PQ: 0 ANSI: 2
Aug 31 10:51:50 merkaba kernel: [216780.938602] sd 13:0:0:0: Attached scsi generic \
                sg3 type 0
Aug 31 10:51:50 merkaba kernel: [216780.940382] sd 13:0:0:1: Attached scsi generic \
                sg4 type 0
Aug 31 10:51:50 merkaba kernel: [216780.942365] sd 13:0:0:2: Attached scsi generic \
                sg5 type 0
Aug 31 10:51:50 merkaba kernel: [216780.945763] sd 13:0:0:0: [sdc] Attached SCSI \
                removable disk
Aug 31 10:51:50 merkaba kernel: [216780.947310] sd 13:0:0:3: Attached scsi generic \
                sg6 type 0
Aug 31 10:51:50 merkaba kernel: [216780.948245] sd 13:0:0:4: Attached scsi generic \
                sg7 type 0
Aug 31 10:51:50 merkaba kernel: [216780.948512] sd 13:0:0:2: [sde] Attached SCSI \
                removable disk
Aug 31 10:51:50 merkaba kernel: [216780.949139] sd 13:0:0:1: [sdd] Attached SCSI \
                removable disk
Aug 31 10:51:50 merkaba kernel: [216780.952637] sd 13:0:0:3: [sdf] Attached SCSI \
                removable disk
Aug 31 10:51:50 merkaba kernel: [216780.954517] sd 13:0:0:4: [sdg] Attached SCSI \
removable disk


merkaba:~> tail -fn0 /var/log/kern.log
Aug 31 10:54:39 merkaba kernel: [216949.712566] sd 14:0:0:1: [sdd] 2048 512-byte \
                logical blocks: (1.04 MB/1.00 MiB)
Aug 31 10:54:39 merkaba kernel: [216949.717781]  sdd: sdd1
Aug 31 10:54:39 merkaba kernel: [216949.717841] sdd: p1 start 32768 is beyond EOD, \
                enabling native capacity
Aug 31 10:54:39 merkaba kernel: [216949.721094]  sdd: sdd1
Aug 31 10:54:39 merkaba kernel: [216949.721129] sdd: p1 start 32768 is beyond EOD, \
truncated

Lol, can ´t read this SDXC card it seems. :)


[1] git@gitorious.org:flashbench-martin21/flashbench.git

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

_______________________________________________
Flashbench-results mailing list
Flashbench-results@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/flashbench-results


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic