where to ask for support?

[jobenvil]

Hi @tobetter where is the place to post or ask for help where you are active?
I would ask which kernel starts to supports uas on odroidxu4? I see on def_conf is istill uncommented. I have usb device controller (JMicron 567) which supports scsi + uas. Thanks!

[tobetter]

@jobenvil it's ok to post here your questions or drop me an email any time. As of now, I've not tested UAS yet. So no proof XU4 kernel can support it perfectly as of now.

[jobenvil]

Thanks Kim.

Enabling in .config CONFIG_USB_UAS=y I have no succes, even with 4.7.-rc.2-next.

I bought two different USB-SATA-Adapter which should support uas:

• JMicron USA Technology Corp. JMS567

root@hiperborea ~ # lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 0bda:8153 Realtek Semiconductor Corp.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 004: ID 152d:3562 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Bus 004 Device 003: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

root@hiperborea ~ # lsusb -vvv -d   152d:3562 | grep -ie 'id\|maxpower\|streams\|protocol'
Bus 004 Device 004: ID 152d:3562 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
  bDeviceProtocol         0
  idVendor           0x152d JMicron Technology Corp. / JMicron USA Technology Corp.
  idProduct          0x3562 JMS567 SATA 6Gb/s bridge
    MaxPower                2mA
      bInterfaceProtocol     80 Bulk-Only
      bInterfaceProtocol     98
        MaxStreams             32
        MaxStreams             32
        MaxStreams             32

and

• ASMedia Technology Inc. ASM1153 SATA 3Gb/s bridge

root@hiperborea ~ # lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 0bda:8153 Realtek Semiconductor Corp.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge
Bus 004 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


root@hiperborea ~ # lsusb -vvv -d  174c:55aa | grep -ie 'id\|maxpower\|streams\|protocol'
Bus 004 Device 003: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge
  bDeviceProtocol         0
  idVendor           0x174c ASMedia Technology Inc.
  idProduct          0x55aa ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge
    MaxPower                0mA
      bInterfaceProtocol     80 Bulk-Only
      bInterfaceProtocol     98
        MaxStreams             32
        MaxStreams             32
        MaxStreams             32

but kernel messages indicate that uas will not work and therefore Bulk-Only protocol will rule:

[    4.404523] usb 4-1.1: new SuperSpeed USB device number 3 using xhci-hcd
[    4.431002] usb 4-1.1: New USB device found, idVendor=174c, idProduct=55aa
[    4.441566] usb 4-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    4.452431] usb 4-1.1: Product: ASMT1051
[    4.459905] usb 4-1.1: Manufacturer: asmedia
[    4.467710] usb 4-1.1: SerialNumber: 12345678DCA3
[    4.479543] usb 4-1.1: USB controller xhci-hcd.2.auto does not support streams, which are required by the UAS driver.
[    4.493897] usb 4-1.1: Please try an other USB controller if you wish to use UAS.
[    4.505279] usb 4-1.1: USB controller xhci-hcd.2.auto does not support streams, which are required by the UAS driver.
[    4.519732] usb 4-1.1: Please try an other USB controller if you wish to use UAS.

According to MaxPower = 0 mW and uas-detect.h , I should have the ASM1153. Some hint or direction to dig? Thanks in advance.

[tobetter]

Hey @jobenvil,

What's the product of ASM1153?
Any reason you have to use ASM1153, not JMS567?

[jobenvil]

No special reason, I just bought to test them because they have USB attached SCSI support.

• ASM1153 is from StarTech and JM567 is from Inateck

Update: With iotf master branch 4.6.0+ are recogniced both adapters like USB Attached SCSI / uas:

• Example lsusb -v JM567:

Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       1
      bNumEndpoints           4
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     98
      iInterface             10 MSC USB Attached SCSI

dmesg JM567

[    8.665627] usb 4-1.1: new SuperSpeed USB device number 3 using xhci-hcd
[    8.686851] usb 4-1.1: New USB device found, idVendor=152d, idProduct=3562
[    8.692283] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    8.699563] usb 4-1.1: Product: AD TO BE II
[    8.703713] usb 4-1.1: Manufacturer: ADMKIV
[    8.707874] usb 4-1.1: SerialNumber: DB123456789628
[    8.724382] scsi host0: uas
[    8.727286] scsi 0:0:0:0: Direct-Access     ADplus   SuperVer         6302 PQ: 0 ANSI: 6
[    8.767014] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[    8.767224] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    8.778375] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    8.784305] sd 0:0:0:0: [sda] Write Protect is off
[    8.788308] sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08
[    8.788680] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    8.881738]  sda: sda1 sda2
[    8.885725] sd 0:0:0:0: [sda] Attached SCSI disk
...
...
[   12.901106] usbcore: registered new interface driver r8152
[   12.931370] usbcore: registered new interface driver cdc_ether
[   13.098440] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
[   13.185062] r8152 6-1:1.0 eth0: v1.08.3
[   13.402296] usb 4-1.1: USB disconnect, device number 3
[   13.421351] sd 0:0:0:0: [sda] tag#0 uas_zap_pending 0 uas-tag 1 inflight: CMD
[   13.421376] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 01 10 00 00 f0 00
[   13.421407] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[   13.421420] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 01 10 00 00 f0 00
[   13.421430] blk_update_request: I/O error, dev sda, sector 272
[   13.426899] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[   13.565685] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00
[   17.135625] usb 4-1.1: new SuperSpeed USB device number 4 using xhci-hcd
[   17.151751] usb 4-1.1: New USB device found, idVendor=152d, idProduct=3562
[   17.151765] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   17.151774] usb 4-1.1: Product: AD TO BE II
[   17.151783] usb 4-1.1: Manufacturer: ADMKIV
[   17.151793] usb 4-1.1: SerialNumber: DB123456789628
[   17.155010] scsi host0: uas
[   17.157219] scsi 0:0:0:0: Direct-Access     ADplus   SuperVer         6302 PQ: 0 ANSI: 6
[   17.206579] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   17.206749] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[   17.206769] sd 0:0:0:0: [sda] 4096-byte physical blocks
[   17.207577] sd 0:0:0:0: [sda] Write Protect is off
[   17.207593] sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08
[   17.207997] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   17.269708]  sda: sda1 sda2
[   17.272640] sd 0:0:0:0: [sda] Attached SCSI disk

• ASMedia ASM1153:

[    3.534477] usb 4-1.1: new SuperSpeed USB device number 3 using xhci-hcd
[    3.555420] usb 4-1.1: New USB device found, idVendor=174c, idProduct=55aa
[    3.561388] usb 4-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    3.568613] usb 4-1.1: Product: ASMT1051
[    3.572096] usb 4-1.1: Manufacturer: asmedia
[    3.576515] usb 4-1.1: SerialNumber: 12345678DCA3
[    3.593457] scsi host0: uas
[    3.595907] scsi 0:0:0:0: Direct-Access     ASMT     2115             0    PQ: 0 ANSI: 6
[    3.615155] random: nonblocking pool is initialized
[    3.646398] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    3.646614] sd 0:0:0:0: [sda] Spinning up disk...
[    4.024476] raid6: int32x1  gen()   429 MB/s
[    4.109377] raid6: int32x1  xor()   325 MB/s
[    4.194421] raid6: int32x2  gen()   625 MB/s
[    4.279385] raid6: int32x2  xor()   471 MB/s
[    4.364420] raid6: int32x4  gen()   719 MB/s
[    4.449358] raid6: int32x4  xor()   581 MB/s
[    4.534393] raid6: int32x8  gen()   947 MB/s
[    4.619338] raid6: int32x8  xor()   592 MB/s
[    4.622125] raid6: using algorithm int32x8 gen() 947 MB/s
[    4.627518] raid6: .... xor() 592 MB/s, rmw enabled
[    4.632370] raid6: using intx1 recovery algorithm
[    4.637818] xor: measuring software checksum speed
[    4.649400] .
[    4.689356]    arm4regs  :  2943.200 MB/sec
[    4.739369]    8regs     :  2458.400 MB/sec
[    4.789342]    32regs    :  2351.200 MB/sec
[    4.792046] xor: using function: arm4regs (2943.200 MB/sec)
[    4.810989] Btrfs loaded, assert=on
[    5.654403] ....ready
[    8.670778] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[    8.677382] sd 0:0:0:0: [sda] Write Protect is off
[    8.681583] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[    8.681878] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    8.800104]  sda: sda1 sda2
[    8.803908] sd 0:0:0:0: [sda] Attached SCSI disk

and corresponding lsusb -v:

    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       1
      bNumEndpoints           4
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     98
      iInterface              0

I cannot update you about the uas performance compared with other kernels since I don't have a stable environment to test them. When I have it, I will update you. You may like close the issue.

[tobetter]

@jobenvil Ok, thank you for update. I recently got a board of JMicro, different chipset with yours. I was planning to adapt it to XU4. FYI, I've started to create a branch with v4.6 recently, hope it could work.
https://github.com/tobetter/linux/commits/odroidxu4-v4.6

[jobenvil]

FYI, I've started to create a branch with v4.6 recently, hope it could work.
https://github.com/tobetter/linux/commits/odroidxu4-v4.6

@tobetter thank you, this will be very usefull since I'm still testing.

[uDude]

Ams1053 works well but does not have pm.
On Jun 14, 2016 5:02 AM, "José Benlloch" notifications@github.com wrote:

FYI, I've started to create a branch with v4.6 recently, hope it could
work.
https://github.com/tobetter/linux/commits/odroidxu4-v4.6

@tobetter https://github.com/tobetter thank you, this will be very
usefull since I'm still testing.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#5 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AIiMeCKi486kmRnFYru-TlcslWieyyKQks5qLopOgaJpZM4IpQzo
.

[tobetter]

@uDude could you share more detail about your running environment? Like kernel version and platform?
@jobenvil would you mind to share your expectation in terms of the performance and how you are planning to measure it?

[uDude]

Sure,

I have xu4 to an asmedia 1053 based chip set (
http://www.datoptic.com/ec/usb3-to-sata3-6gb-s-bridge.html). This connects
to western digital red 3T disks.

Kernel is the tobetter 4.2.x.

I get about 144 MB/s write speed.

I am using CloudDB, Ubuntu 16.04. These are server only so I cannot
comment on sound or video.
On Jun 14, 2016 6:48 AM, "Dongjin Kim" notifications@github.com wrote:

@uDude https://github.com/uDude could you share more detail about your
running environment? Like kernel version and platform?
@jobenvil https://github.com/jobenvil would you mind to share your
expectation in terms of the performance and how you are planning to measure
it?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#5 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AIiMeIHW0UgS9a1G1HovuTWpzgLr0KBiks5qLqMFgaJpZM4IpQzo
.

[jobenvil]

@tobetter I read some time ago this sunxi article regarding UASP and found interesting why not to get enabled in odroidxu4 if is only a matter of find out a working UAS adapter. After that, @tkaiser from ARMBIAN asked in ODROID Forum for check the uas performance in OdroidXU4 devices. This is the history behind.

and how you are planning to measure it?

Don't expect more than what I know, like hdparm, dd, iozone, HELIOS LanTest. Basically blocking the uas on kernel module load. @uDude if you have uas enabled, can you try blacklisting the uas module and test performance w/o?

would you mind to share your expectation in terms of the performance

UAS is really performing better than w/o. Check the notes here. On Lemaker Banana Pro running Kernel 4.6.2 / Ubuntu 16.04 using the USB2.0 ports with JM567 I got around 40MB/S for write and read, what it is worth to consider the re-use of the USB2.0 ports again.

[uDude]

Hmmmm,

I do my builds on the XU4 and somewhere in the recent commits the kernel
compile is broken. See below:

drivers/phy/phy-exynos5-usbdrd.c: In function
‘exynos5420_usbdrd_phy_calibrate’:
drivers/phy/phy-exynos5-usbdrd.c:652:10: warning: ‘return’ with a value, in
function returning void
return ret;
^
drivers/phy/phy-exynos5-usbdrd.c:666:10: warning: ‘return’ with a value, in
function returning void
return ret;
^
drivers/phy/phy-exynos5-usbdrd.c:699:9: warning: ‘return’ with a value, in
function returning void
return ret;
^
drivers/phy/phy-exynos5-usbdrd.c: At top level:
drivers/phy/phy-exynos5-usbdrd.c:804:28: error: initialization from
incompatible pointer type [-Werror=incompatible-pointer-types]
.phy_exynos_calibrate = exynos5420_usbdrd_phy_calibrate,
^
drivers/phy/phy-exynos5-usbdrd.c:804:28: note: (near initialization for
‘exynos5420_usbdrd_phy.phy_exynos_calibrate’)

I didn't think the aufs patch updated the usbdrd. Regardless, when I get a
chance I have a separate branch that compiles that I'll enable the
requested changes on and let you know. I want to do the speed tests
against identical kernels with only that one difference.

I had terrible performance with some jmicro chipsets, but the ASMedia
1053 (no port-multiplier) works great for me.

It will be a few days be patient and I'll get you the requested
comparisons. Note my builds giving 140 MB/s (not 140 Mb/s) are using the
@tobetter defconfig.

uDude

On Tue, Jun 14, 2016 at 10:03 PM, José Benlloch notifications@github.com
wrote:

@tobetter https://github.com/tobetter I read some time ago this sunxi
article regarding UASP http://linux-sunxi.org/USB/UAS and found
interesting why not to get enabled in odroidxu4 if is only a matter of find
out a working UAS adapter. After that, @tkaiser from ARMBIAN asked in
ODROID Forum http://forum.odroid.com/viewtopic.php?f=97&t=17349 for
check the uas performance in OdroidXU4 devices. This is the history behind.

and how you are planning to measure it?

Don't expect more than what I know, like hdparm, dd, iozone, HELIOS
LanTest. Basically blocking the uas on kernel module load. @uDude
https://github.com/uDude if you have uas enabled, can you try
blacklisting the uas module and test performance w/o?

would you mind to share your expectation in terms of the performance

UAS is really performing better than w/o. Check the notes here.
http://pastebin.com/aGZyeryT On Lemaker Banana Pro running Kernel 4.6.2
/ Ubuntu 16.04 using the USB2.0 ports with JM567 I got around 40MB/S for
write and read, what it is worth to consider the re-use of the USB2.0 ports
again.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#5 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AIiMeIKll4Ek5BRzRsT8e0iTI74tAZKsks5qLyUzgaJpZM4IpQzo
.

[uDude]

Change the return value of the function to static int from static void and
all is well. I say that w/o testing only that the build completes.

On Wed, Jun 15, 2016 at 1:55 AM, Mike Kyle mfkyle@gmail.com wrote:

Hmmmm,

I do my builds on the XU4 and somewhere in the recent commits the kernel
compile is broken. See below:

drivers/phy/phy-exynos5-usbdrd.c: In function
‘exynos5420_usbdrd_phy_calibrate’:
drivers/phy/phy-exynos5-usbdrd.c:652:10: warning: ‘return’ with a value,
in function returning void
return ret;
^
drivers/phy/phy-exynos5-usbdrd.c:666:10: warning: ‘return’ with a value,
in function returning void
return ret;
^
drivers/phy/phy-exynos5-usbdrd.c:699:9: warning: ‘return’ with a value, in
function returning void
return ret;
^
drivers/phy/phy-exynos5-usbdrd.c: At top level:
drivers/phy/phy-exynos5-usbdrd.c:804:28: error: initialization from
incompatible pointer type [-Werror=incompatible-pointer-types]
.phy_exynos_calibrate = exynos5420_usbdrd_phy_calibrate,
^
drivers/phy/phy-exynos5-usbdrd.c:804:28: note: (near initialization for
‘exynos5420_usbdrd_phy.phy_exynos_calibrate’)

I didn't think the aufs patch updated the usbdrd. Regardless, when I get
a chance I have a separate branch that compiles that I'll enable the
requested changes on and let you know. I want to do the speed tests
against identical kernels with only that one difference.

I had terrible performance with some jmicro chipsets, but the ASMedia
1053 (no port-multiplier) works great for me.

It will be a few days be patient and I'll get you the requested
comparisons. Note my builds giving 140 MB/s (not 140 Mb/s) are using the
@tobetter defconfig.

uDude

On Tue, Jun 14, 2016 at 10:03 PM, José Benlloch notifications@github.com
wrote:

@tobetter https://github.com/tobetter I read some time ago this sunxi
article regarding UASP http://linux-sunxi.org/USB/UAS and found
interesting why not to get enabled in odroidxu4 if is only a matter of find
out a working UAS adapter. After that, @tkaiser from ARMBIAN asked in
ODROID Forum http://forum.odroid.com/viewtopic.php?f=97&t=17349 for
check the uas performance in OdroidXU4 devices. This is the history behind.

and how you are planning to measure it?

Don't expect more than what I know, like hdparm, dd, iozone, HELIOS
LanTest. Basically blocking the uas on kernel module load. @uDude
https://github.com/uDude if you have uas enabled, can you try
blacklisting the uas module and test performance w/o?

would you mind to share your expectation in terms of the performance

UAS is really performing better than w/o. Check the notes here.
http://pastebin.com/aGZyeryT On Lemaker Banana Pro running Kernel
4.6.2 / Ubuntu 16.04 using the USB2.0 ports with JM567 I got around 40MB/S
for write and read, what it is worth to consider the re-use of the USB2.0
ports again.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#5 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AIiMeIKll4Ek5BRzRsT8e0iTI74tAZKsks5qLyUzgaJpZM4IpQzo
.

[tobetter]

@uDude I think you need this patch,
13c3c92

Guys, this is good input for me. Actually I am not very expert at such performance tuning and integration, but very interesting...I don't have ASMedia device, would try to purchase if possible to compare with JMicron.

Please keep me in your track. I hope to share you guys with v4.6 kernel in debian or Ubuntu server on next week if possible.

[uDude]

I have two 4.6 kernels ready to test. I need to obtain an adaptor with a
chipset that supports UASP. My ASMEDIA 1053 does not. The 1053E does. I
prefer to stick with a chipset that I know works well with the xu4 ss chip.

I'll scour amazon and see what I can find. If this works It will be worth
the $$ for me. If you know of one please drop me a line.

On Wed, Jun 15, 2016 at 2:29 AM, Mike Kyle mfkyle@gmail.com wrote:

Change the return value of the function to static int from static void and
all is well. I say that w/o testing only that the build completes.

On Wed, Jun 15, 2016 at 1:55 AM, Mike Kyle mfkyle@gmail.com wrote:

Hmmmm,

I do my builds on the XU4 and somewhere in the recent commits the kernel
compile is broken. See below:

drivers/phy/phy-exynos5-usbdrd.c: In function
‘exynos5420_usbdrd_phy_calibrate’:
drivers/phy/phy-exynos5-usbdrd.c:652:10: warning: ‘return’ with a value,
in function returning void
return ret;
^
drivers/phy/phy-exynos5-usbdrd.c:666:10: warning: ‘return’ with a value,
in function returning void
return ret;
^
drivers/phy/phy-exynos5-usbdrd.c:699:9: warning: ‘return’ with a value,
in function returning void
return ret;
^
drivers/phy/phy-exynos5-usbdrd.c: At top level:
drivers/phy/phy-exynos5-usbdrd.c:804:28: error: initialization from
incompatible pointer type [-Werror=incompatible-pointer-types]
.phy_exynos_calibrate = exynos5420_usbdrd_phy_calibrate,
^
drivers/phy/phy-exynos5-usbdrd.c:804:28: note: (near initialization for
‘exynos5420_usbdrd_phy.phy_exynos_calibrate’)

I didn't think the aufs patch updated the usbdrd. Regardless, when I get
a chance I have a separate branch that compiles that I'll enable the
requested changes on and let you know. I want to do the speed tests
against identical kernels with only that one difference.

I had terrible performance with some jmicro chipsets, but the ASMedia
1053 (no port-multiplier) works great for me.

It will be a few days be patient and I'll get you the requested
comparisons. Note my builds giving 140 MB/s (not 140 Mb/s) are using the
@tobetter defconfig.

uDude

On Tue, Jun 14, 2016 at 10:03 PM, José Benlloch <notifications@github.com

wrote:

@tobetter https://github.com/tobetter I read some time ago this sunxi
article regarding UASP http://linux-sunxi.org/USB/UAS and found
interesting why not to get enabled in odroidxu4 if is only a matter of find
out a working UAS adapter. After that, @tkaiser from ARMBIAN asked in
ODROID Forum http://forum.odroid.com/viewtopic.php?f=97&t=17349 for
check the uas performance in OdroidXU4 devices. This is the history behind.

and how you are planning to measure it?

Don't expect more than what I know, like hdparm, dd, iozone, HELIOS
LanTest. Basically blocking the uas on kernel module load. @uDude
https://github.com/uDude if you have uas enabled, can you try
blacklisting the uas module and test performance w/o?

would you mind to share your expectation in terms of the performance

UAS is really performing better than w/o. Check the notes here.
http://pastebin.com/aGZyeryT On Lemaker Banana Pro running Kernel
4.6.2 / Ubuntu 16.04 using the USB2.0 ports with JM567 I got around 40MB/S
for write and read, what it is worth to consider the re-use of the USB2.0
ports again.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#5 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AIiMeIKll4Ek5BRzRsT8e0iTI74tAZKsks5qLyUzgaJpZM4IpQzo
.

[jobenvil]

Some comments:

I had terrible performance with some jmicro chipsets, but the ASMedia 1053 (no port-multiplier) works great for me.

Yes, but newer JMicron chipsets performs well, see these chipsets here and explained. In the past some UAS ASMedia Chipset were blacklisted. Ensure that you get ASM1153 chip and it will work with UAS.

I want to do the speed tests against identical kernels with only that one difference.

Thats the point. It is not a matter of max read/write results, instead a porcentual gain since the other parameters depend on harddisk model, filesystem, I/O scheduler, mounting flags, etc. Don't expect more gain with UAS if your maximal specifications for your hardrive are already 140MB/s as well

I'll scour amazon and see what I can find. If this works It will be worth the $$ for me. If you know of one please drop me a line.

I have these two which really support UAS. See my third post.