public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hans Petter Selasky <hps@selasky.org>
Cc: bugzilla-daemon@kernel.org, linux-usb@vger.kernel.org
Subject: Re: [Bug 217242] CPU hard lockup related to xhci/dma
Date: Sun, 2 Apr 2023 19:25:27 +0200	[thread overview]
Message-ID: <2023040210-armband-spiffy-b5a5@gregkh> (raw)
In-Reply-To: <7dc47823-01a1-ac19-73d4-4bf7eb07f98d@selasky.org>

On Sun, Apr 02, 2023 at 05:54:18PM +0200, Hans Petter Selasky wrote:
> While that being said, I wish the Linux USB core would take the example of
> the FreeBSD USB core, and pre-allocate all memory needed for USB transfers,
> also called URB's, during device attach.

Many drivers do that today already, which specific ones do you think
need to have this added that are not doing so?

> Frequently going through allocate
> and free cycles during operation, is not just inefficient, but also greatly
> degrades the ability to debug the system.

Based on the slow USB speeds, "inefficient" isn't anything that I've
been able to measure specifically, have you?

> USB is still quite essential when doing remote server access. Yeah,
> the serial port is great too, but one day inb() and outb() will die

That's what a USB debugging cable is for :)

thanks,

greg k-h

  reply	other threads:[~2023-04-02 17:25 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 15:00 [Bug 217242] New: CPU hard lockup related to xhci/dma bugzilla-daemon
2023-04-01 20:49 ` [Bug 217242] " bugzilla-daemon
2023-04-01 20:54 ` bugzilla-daemon
2023-04-01 20:57 ` bugzilla-daemon
2023-04-01 22:11 ` bugzilla-daemon
2023-04-01 22:12 ` bugzilla-daemon
2023-04-01 22:17 ` bugzilla-daemon
2023-04-02 15:54   ` Hans Petter Selasky
2023-04-02 17:25     ` Greg KH [this message]
2023-04-02 18:57       ` Alan Stern
2023-04-05 18:15         ` Hans Petter Selasky
2023-04-02 15:54 ` bugzilla-daemon
2023-04-02 17:25 ` bugzilla-daemon
2023-04-03 19:18 ` bugzilla-daemon
2023-04-06 20:15 ` bugzilla-daemon
2023-04-06 20:16 ` bugzilla-daemon
2023-04-10 17:32 ` bugzilla-daemon
2023-04-10 17:34 ` bugzilla-daemon
2023-04-11 12:54 ` bugzilla-daemon
2023-04-12 19:56 ` bugzilla-daemon
2023-04-12 19:57 ` bugzilla-daemon
2023-04-13  8:02 ` bugzilla-daemon
2023-04-13 20:23 ` bugzilla-daemon
2023-04-14 14:24 ` bugzilla-daemon
2023-04-14 14:32 ` bugzilla-daemon
2023-04-14 20:02 ` bugzilla-daemon
2023-04-18 19:24 ` bugzilla-daemon
2023-04-18 20:17 ` bugzilla-daemon
2023-04-19 15:41 ` bugzilla-daemon
2023-04-19 15:44 ` bugzilla-daemon
2023-04-19 18:41 ` bugzilla-daemon
2023-04-19 18:45 ` bugzilla-daemon
2023-04-21 17:54 ` bugzilla-daemon
2023-04-25 14:35 ` bugzilla-daemon
2023-04-25 19:01 ` bugzilla-daemon
2023-04-26 15:18 ` bugzilla-daemon
2023-04-26 15:20 ` bugzilla-daemon
2023-04-27 20:37 ` bugzilla-daemon
2023-05-05 18:50 ` bugzilla-daemon
2023-05-08  7:54 ` bugzilla-daemon
2023-05-08 11:46 ` bugzilla-daemon

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=2023040210-armband-spiffy-b5a5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bugzilla-daemon@kernel.org \
    --cc=hps@selasky.org \
    --cc=linux-usb@vger.kernel.org \
    /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