From: Marcello Sylvester Bauer <sylv@sylv.io>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Marcello Sylvester Bauer <marcello.bauer@9elements.com>,
Matthias Stoeckl <matthias.stoeckl@secunet.com>,
Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de>,
Marcello Sylvester Bauer <sylv@sylv.io>
Subject: [PATCH v1 0/2] usb: gadget: dummy_hcd: Switch to hrtimers for better performance
Date: Thu, 11 Apr 2024 17:22:09 +0200 [thread overview]
Message-ID: <cover.1712843963.git.sylv@sylv.io> (raw)
About 10 years ago, there was a discussion about the poor performance
of dummy_hcd due to the use of jiffies instead of hrtimers [1].
There was a proposal to switch to hrtimers, but the patch never made it
into the mainline, and I cannot figure out why.
This patch set brings the idea back to the mailing list with the
intention of improving the overall performance of this driver.
[1](https://linux-usb.vger.kernel.narkive.com/Fdt5oBR8/dummy-hcd-performance-correctness)
Marcello Sylvester Bauer (2):
usb: gadget: dummy_hcd: Switch to hrtimer transfer scheduler
usb: gadget: dummy_hcd: Set transfer interval to 1 microframe
drivers/usb/gadget/udc/dummy_hcd.c | 37 ++++++++++++++++++------------
1 file changed, 22 insertions(+), 15 deletions(-)
--
2.44.0
next reply other threads:[~2024-04-11 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 15:22 Marcello Sylvester Bauer [this message]
2024-04-11 14:51 ` [PATCH v1 1/2] usb: gadget: dummy_hcd: Switch to hrtimer transfer scheduler Marcello Sylvester Bauer
2024-04-11 15:22 ` Marcello Sylvester Bauer
2024-04-11 16:30 ` Alan Stern
2024-04-11 14:51 ` [PATCH v1 2/2] usb: gadget: dummy_hcd: Set transfer interval to 1 microframe Marcello Sylvester Bauer
2024-04-11 15:22 ` Marcello Sylvester Bauer
2024-04-11 16:21 ` Alan Stern
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=cover.1712843963.git.sylv@sylv.io \
--to=sylv@sylv.io \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marcello.bauer@9elements.com \
--cc=matthias.stoeckl@secunet.com \
--cc=u.kleine-koenig@pengutronix.de \
/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.