From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Greg KH <gregkh@suse.de>
Cc: Timur Tabi <timur@freescale.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How important is it that tty_write_room doesn't lie?
Date: Thu, 24 Feb 2011 11:29:02 +0000 [thread overview]
Message-ID: <20110224112902.71047445@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20110223202915.GB9081@suse.de>
> I think that people don't normally hit this as the console code isn't
> used as a tty and a console at the same time, right?
And also on most hardware that it doesn't actually matter.
The underlying logic is that printk output is important, and Linus has
always insisted that what matters is that it gets out, even with
collateral damage be that vt output mangling or serial losses.
If it's an actual problem in your environment you could do a bit of quiet
internal buffering (or report less than you really have if your fifo
queue is big)
Alan
prev parent reply other threads:[~2011-02-24 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 19:56 Timur Tabi
2011-02-23 20:29 ` Greg KH
2011-02-23 20:48 ` Timur Tabi
2011-02-23 22:57 ` Ted Ts'o
2011-02-24 12:34 ` Theodore Tso
2011-02-23 23:17 ` Greg KH
2011-02-24 11:29 ` 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=20110224112902.71047445@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=timur@freescale.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
all inboxes | Powered by JetHome®