linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Brauch <mail@svenbrauch.de>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Oliver Neukum <oneukum@suse.com>, Johan Hovold <johan@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	Toby Gray <toby.gray@realvnc.com>,
	linux-usb@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] Fix data loss in cdc-acm
Date: Thu, 23 Jul 2015 00:53:18 +0200	[thread overview]
Message-ID: <55B01EDE.3050503@svenbrauch.de> (raw)
In-Reply-To: <55B01554.90201@hurleysoftware.com>

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

Hi,

On 23/07/15 00:12, Peter Hurley wrote:
> The premature unthrottle actually leads to the data loss but the throttling
> with a mere 2K left is _way too late_.
Ok, yes, I think so too.

> 10ms is a _really_ long time for a cpu not to attend to a kworker.
> Which raises 2 questions:
> 1. What are the termios settings of the tty receiving input? Is it 'raw'
>    mode or typical terminal mode (icanon, echo, etc.) or something else?
In my test code, I open the tty like
  fd = open("/dev/ttyACM0", O_RDWR | O_NOCTTY | O_NONBLOCK);
I don't make any other changes to the default settings. To be honest,
I'm not sure in which mode it is operating then (I was assuming raw, but
I might be wrong?).

> 2. Are there RT threads that are hogging cpu time?
I can't see any, I think the only thing which occasionally goes to RT is
pulseaudio (but during at least some of the tests I wasn't even playing
audio, so that sounds very unplausible to me). I also cannot see a
correlation between failure rate and CPU load.

Best regards,
Sven


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-07-22 22:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19 21:37 [PATCH] Fix data loss in cdc-acm Sven Brauch
2015-07-20 17:25 ` Johan Hovold
2015-07-20 18:07   ` Sven Brauch
2015-07-21  9:18     ` Johan Hovold
2015-07-21 16:45       ` Peter Hurley
2015-07-22  8:40         ` Oliver Neukum
2015-07-22 14:30           ` Peter Hurley
2015-07-22 15:01             ` Oliver Neukum
2015-08-05  0:26               ` Peter Hurley
2015-07-21 13:43     ` Oliver Neukum
2015-07-21 21:43       ` Sven Brauch
2015-07-21 23:34         ` Peter Hurley
2015-07-22  0:47           ` Sven Brauch
2015-07-22 22:12             ` Peter Hurley
2015-07-22 22:53               ` Sven Brauch [this message]
2015-07-27 10:00                 ` Peter Stuge
2015-08-05 17:36                 ` Peter Hurley
2015-10-20 18:16                   ` Peter Hurley
2015-10-21 10:12                     ` Oliver Neukum
2015-10-21 12:09                       ` Peter Hurley
2015-10-21 14:58                         ` Peter Hurley

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=55B01EDE.3050503@svenbrauch.de \
    --to=mail@svenbrauch.de \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=peter@hurleysoftware.com \
    --cc=toby.gray@realvnc.com \
    /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).