Linux USB
 help / color / mirror / Atom feed
From: ValdikSS <iam@valdikss.org.ru>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>, linux-usb@vger.kernel.org
Subject: Re: USB 1.1 Full Speed OHCI slow/high latency
Date: Mon, 22 Sep 2025 17:38:38 +0300	[thread overview]
Message-ID: <c8e00367-35c8-49df-9fef-a93cdcde354a@valdikss.org.ru> (raw)
In-Reply-To: <d689fcb8-20c7-4a81-a466-7492eaa23567@rowland.harvard.edu>

On 22.09.2025 5:16 PM, Alan Stern wrote:
> On Mon, Sep 22, 2025 at 02:11:43AM +0300, ValdikSS wrote:
>> Alan, Greg, I found the reason for 1 ms delay: it is artificial, added in
>> v2.5.21 as a possible race condition fix:
> 
> Good work tracking that down!
> 
>> I removed "+ 1" and it removed that 1ms delay. Doesn't seem to break
>> anything in my setup. UHCI code doesn't seem to have any similar delays.
>>
>> Could it be relevant only for hardware of its era? If I add "no +1" code
>> quirk as a module option, disabled by default, does it sounds sane to you?
> 
> I'm not sure that there is any OHCI hardware from later than that era.
> But regardless...
> 
> Module options are frowned upon these days.  Instead you could add a
> sysfs (or even debugfs) attribute file for controlling that "+ 1".

I just implemented another approach: do not unlink the ED right away, 
instead mark it IDLE and unlink only if no consecutive transfers are 
performed after the timeout. This still preserves one-frame delay while 
unlinking, should be safe.

Please take a look if you have free time. I'm no kernel developer by any 
means :)


  reply	other threads:[~2025-09-22 14:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14  1:56 USB 1.1 Full Speed OHCI slow/high latency ValdikSS
2025-08-14  6:01 ` Greg KH
2025-08-14 14:24 ` Alan Stern
2025-08-14 15:11   ` ValdikSS
2025-08-14 16:40     ` Alan Stern
2025-08-15  8:39       ` ValdikSS
2025-08-15 14:52         ` Alan Stern
2025-08-15 15:53           ` ValdikSS
2025-08-15 17:07             ` Alan Stern
2025-08-15 18:13               ` ValdikSS
2025-08-16  2:04                 ` Alan Stern
2025-09-21 23:11                   ` ValdikSS
2025-09-22 14:16                     ` Alan Stern
2025-09-22 14:38                       ` ValdikSS [this message]
2025-09-22 14:43                         ` Alan Stern
2025-09-22 14:48                           ` [PATCH] usb: ohci: delay endpoint descriptor unlinking to reduce transfer latency ValdikSS
2025-10-01 19:27                             ` Alan Stern
2025-10-01 22:34                               ` [PATCH v2] " ValdikSS
2025-10-02 17:05                                 ` Alan Stern
2025-10-22 13:39                               ` [PATCH v2 RESEND] " ValdikSS

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=c8e00367-35c8-49df-9fef-a93cdcde354a@valdikss.org.ru \
    --to=iam@valdikss.org.ru \
    --cc=greg@kroah.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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