From: Paul Fulghum <paulkf@microgate.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: tty buffering limit
Date: Fri, 28 Jul 2006 10:36:39 -0500 [thread overview]
Message-ID: <44CA2F07.4020908@microgate.com> (raw)
In-Reply-To: <1154094816.13509.132.camel@localhost.localdomain>
Alan Cox wrote:
> Certain people seem to have assumed tty->throttled was 'advisory'. In
> the absence of tty->author->throttle(), it seems we should keep a simple
> limit of our own to avoid problems when this occurs.
Looks reasonable as a general failsafe. There
may be other pathological cases it protects against.
I'll start banging on it.
--
Paul Fulghum
Microgate Systems, Ltd.
prev parent reply other threads:[~2006-07-28 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 16:07 Success: tty_io flush_to_ldisc() error message triggered Chuck Ebbert
2006-07-22 16:41 ` Paul Fulghum
2006-07-25 18:41 ` [stable] " Greg KH
2006-07-25 19:12 ` Paul Fulghum
2006-07-26 7:16 ` Greg KH
[not found] ` <1153941029.6903.5.camel@amdx2.microgate.com>
2006-07-28 13:53 ` [PATCH]: tty buffering limit Alan Cox
2006-07-28 15:36 ` Paul Fulghum [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=44CA2F07.4020908@microgate.com \
--to=paulkf@microgate.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.