From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Stas Sergeev <stsp@list.ru>
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 21:15:09 +0100 [thread overview]
Message-ID: <20120810211509.34cc723e@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <502566EB.3070304@list.ru>
> 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.
I guess providing you account the fifo, and any hardware flow control it
would work.
prev parent reply other threads:[~2012-08-10 20:10 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
2012-08-10 20:15 ` Alan Cox [this message]
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=20120810211509.34cc723e@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=stsp@list.ru \
/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