From: Felipe Balbi <balbi@kernel.org>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>, linux-usb@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: usb: gadget: u_serial: process RX in workqueue instead of tasklet
Date: Mon, 17 Dec 2018 08:59:42 +0200 [thread overview]
Message-ID: <87o99kzli9.fsf@linux.intel.com> (raw)
Hi,
Michał Mirosław <mirq-linux@rere.qmqm.pl> writes:
> Switch RX processing from tasklet to (delayed) work queue. This allows
> receiver more room to process incoming data and prevents flood of
> "ttyGS0: RX not scheduled?" messages on HS receive on slow CPU.
>
> A side effect is 2.4MB/s zmodem transfer speed (up from 1.8MB/s)
> on my test board.
>
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
how have you tested this? Specially, how have you measured throughput? I
want to try and reproduce it here.
next reply other threads:[~2018-12-17 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 6:59 Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-17 13:50 usb: gadget: u_serial: process RX in workqueue instead of tasklet Michał Mirosław
2018-12-16 20:23 Michał Mirosław
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=87o99kzli9.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
/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).