From: Stas Sergeev <stsp@list.ru>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
linux-serial@vger.kernel.org
Subject: Re: Q: how to control the TTY output queue in real time?
Date: Fri, 10 Aug 2012 23:54:19 +0400 [thread overview]
Message-ID: <502566EB.3070304@list.ru> (raw)
In-Reply-To: <20120810203355.224622cc@pyramind.ukuu.org.uk>
Hi Alan, thanks, clear enough now. :)
10.08.2012 23:33, Alan Cox wrote:
> if (bytes_left < constant)
> write_wakeup
>
>
> and I suspect if you made that adjustable and turned off the fifo and any
> other funnies you'd at least make it work for a sufficiently rigged demo.
You suggest to turn off the fifo, sounds worrysome,
does this mean that tcdrain() and TIOCOUTQ do not
account the fifo too?
If they do quite fine with the fifo, then maybe the new
function will do too? Its basically a tcdrain(), just with
the controllable watermark I guess.
next prev parent reply other threads:[~2012-08-10 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 19:17 Q: how to control the TTY output queue in real time? Stas Sergeev
2012-08-10 19:33 ` Alan Cox
2012-08-10 19:54 ` Stas Sergeev [this message]
2012-08-10 20:15 ` Alan Cox
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=502566EB.3070304@list.ru \
--to=stsp@list.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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