From: Alan Stern <stern@rowland.harvard.edu>
To: nana <zhongling0719@126.com>
Cc: gregkh@linuxfoundation.org, USB mailing list <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v6 2/3] usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS
Date: Fri, 16 Sep 2022 13:21:08 -0400 [thread overview]
Message-ID: <YySwhOccJFjfx/Tu@rowland.harvard.edu> (raw)
In-Reply-To: <2fcdca5a-2deb-66ca-fd1d-c3ba719b19af@126.com>
On Fri, Sep 16, 2022 at 02:55:55PM +0800, nana wrote:
> Hi:
>
> ok,I have upated to v7.
>
> Sorry , The information in the previous answers about thinkplus(0x17ef,
> 0x3899) comes from the tester, which is somewhat confused.
>
> I just get the device from other department and the detailed test data
> are as follows:
>
>
> Test the thinkplus(0x17ef, 0x3899) speed by gnome-disk-utility tool.
>
> linux(load uas)： linux(not load uas):
>
> read： 394.2 MB/s read: 382.2 MB/s
>
>
> write: 377.4 MB/s write: 347.8 MB/s
>
>
> ---------------------
>
> win10(lower than linux,but more stable):
>
> read : 388.1 MB/s
>
> write: 320 MB/s
>
>
> The main performance differences is write speed.but load uas can cause error
> after long run, not good compatible with uas, So two bosses can
> consideration for the third patch is it feasible.
Is there any way for you to tell which protocol Windows uses
(usb-storage or UAS)?
Alan Stern
next prev parent reply other threads:[~2022-09-16 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 2:49 [PATCH v6 2/3] usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS Hongling Zeng
2022-09-15 19:32 ` Alan Stern
[not found] ` <2fcdca5a-2deb-66ca-fd1d-c3ba719b19af@126.com>
2022-09-16 17:21 ` Alan Stern [this message]
2022-09-18 12:25 ` zhongling0719
2022-09-22 8:17 ` nana
2022-09-22 15:16 ` Alan Stern
2022-10-31 6:17 ` Juhyung Park
2022-11-09 10:40 ` Greg KH
2022-11-12 7:45 ` zhongling0719
2022-11-12 7:56 ` Greg KH
2023-01-09 12:00 ` Juhyung Park
2023-01-09 11:58 ` Juhyung Park
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=YySwhOccJFjfx/Tu@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=zhongling0719@126.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;
as well as URLs for NNTP newsgroup(s).