From: Toby Gray <toby.gray@realvnc.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Oliver Neukum <oliver@neukum.name>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: cdc-acm: Prevent data loss when filling tty buffer.
Date: Mon, 21 Mar 2011 17:58:33 +0000 [thread overview]
Message-ID: <4D8791C9.1080407@realvnc.com> (raw)
In-Reply-To: <20110321165612.0f764046@lxorguk.ukuu.org.uk>
On 21/03/2011 16:56, Alan Cox wrote:
> On Mon, 21 Mar 2011 15:52:25 +0000
> Toby Gray<toby.gray@realvnc.com> wrote:
>> This patch adds checking for how many bytes have been inserted into the tty
>> buffer and returns any remaining bytes back to the filled read buffer list.
> How does ACM handle flow control - is the expectation that it gets flow
> controlled in hardware by not having the opportunity to send bits
> to the host end ? If so this seems to make sense.
Yes, the expectation is that it is flow controlled in hardware if a bulk
endpoint is used. To this end cdc-acm.ko doesn't issue any new read
requests while the tty is throttled. This works as flow control most of
the time, but not when the data is arriving quickly (a few megabytes per
second).
Thank you for your other comments. I had initially gone for the memmove
thinking that having a buffer head as well as a base would have
needlessly complicated the rest of the code.
Having made the required changes it seems I'd greatly overestimated the
changes and it is definitely far cleaner without the memmove.
Regards,
Toby
next prev parent reply other threads:[~2011-03-21 17:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 15:52 [PATCH] USB: cdc-acm: Prevent data loss when filling tty buffer Toby Gray
2011-03-21 16:56 ` Alan Cox
2011-03-21 17:58 ` Toby Gray [this message]
2011-03-22 8:07 ` Oliver Neukum
2011-03-22 11:07 ` Alan Cox
2011-03-21 18:04 ` [PATCH v2] " Toby Gray
2011-03-22 10:05 ` Johan Hovold
2011-03-22 10:35 ` Alan Cox
2011-03-22 11:34 ` Johan Hovold
2011-03-22 14:11 ` Toby Gray
2011-03-22 18:05 ` Alan Cox
2011-03-22 7:43 ` [PATCH] " Oliver Neukum
2011-03-23 12:15 ` Toby Gray
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=4D8791C9.1080407@realvnc.com \
--to=toby.gray@realvnc.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.name \
/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