All of lore.kernel.org
 help / color / mirror / Atom feed
From: sunghwan jung <onenowy@gmail.com>
To: jilin@nvidia.com
Cc: atanasd@gmail.com, linux-usb@vger.kernel.org,
	stern@rowland.harvard.edu, usb-storage@lists.one-eyed-alien.net
Subject: Re: [PATCH 1/1] usb: storage: Add quirk for Samsung Fit flash
Date: Mon, 12 Sep 2022 21:58:06 +0900	[thread overview]
Message-ID: <20220912125806.7568-1-onenowy@gmail.com> (raw)
In-Reply-To: <095677b6-5b6c-1b35-fe9e-00dcedd0a11f@nvidia.com>

On Mon, Sep 12, 2022 at 7:56 PM Jim Lin <jilin@nvidia.com> wrote:
>On Sat, 2022-09-10 at 20:52 +0900, SungHwan Jung wrote:
>External email: Use caution opening links or attachments
>>I have found that the read rate of "samsung Bar plus" is slower than on windows 11 (210mb/s -> 70mb/s) and recovered by disabling quirks (using /etc/modprobe.d)
>>This patch affects not only "Samsung Flash Driver FIT", but also other usb flash storages. (They may use the same controller?)
>>But I can't reproduce the timeout problem without quirks.
>>Could you provide information to reproduce the timeout problem or logs?
>>It may help us find other solutions to fix it.
>>
>>Thanks,
>>SungHwan.
>Issue was reproduced after device has bad block.
>
>--nvpublic

If bad blocks cause the issue, in my opinion, it's better to apply this quirk by users (additional kernel parameters with a bootloader) if their flash drive has bad blocks, not the kernel patch, because the performance degradation is severe for several USB storage that didn't have bad blocks.

      reply	other threads:[~2022-09-12 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02 14:21 [PATCH 1/1] usb: storage: Add quirk for Samsung Fit flash Jim Lin
2020-03-02 15:46 ` Alan Stern
2020-05-02 13:56 ` Atanas Dinev
2020-05-02 14:38   ` Jim Lin
2022-09-12 12:58     ` sunghwan jung [this message]

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=20220912125806.7568-1-onenowy@gmail.com \
    --to=onenowy@gmail.com \
    --cc=atanasd@gmail.com \
    --cc=jilin@nvidia.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=usb-storage@lists.one-eyed-alien.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.