public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ted Ts'o" <tytso@mit.edu>
To: Timur Tabi <timur@freescale.com>
Cc: Greg KH <gregkh@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How important is it that tty_write_room doesn't lie?
Date: Wed, 23 Feb 2011 17:57:28 -0500	[thread overview]
Message-ID: <20110223225728.GR2924@thunk.org> (raw)
In-Reply-To: <4D657292.6000106@freescale.com>

On Wed, Feb 23, 2011 at 02:48:18PM -0600, Timur Tabi wrote:
> Greg KH wrote:
> > 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?
> 
> That's another thing I never understood.  It's rare for a driver to
> support both the console and tty layers.  The serial core driver
> does that, but I can't find any other examples.  I would think that
> a driver would support both interfaces, because both are needed.
> Simplistically, printk --> console, and printf --> tty.  When would
> ever want user-space support but not kernel support?

When you are supporting a large bank of modems?  A number of the
serial cards were originally created to support 32, 64, 128 serial
ports per PCI board, specifically to drive modems, in the bad old days
of modems.  :-)

And I suspect many modern serial devices are just 8250/16550A based,
so they get the console and userspace serial for free.  A large number
of the more exotic boards were created because the 16550A uart isn't
ideal if you are driving vast number of modems at the same time.

> The FIFO can vary, but it's probably at least 2KB it size.  At
> least, we hope to able to set it to that size in the field.
> Currently, we set it to 4KB.

Wow, the FIFO has gotten a lot larger than I ever remember them
getting even when people were doing 460kbps.  I'm guessing this is
because you're trying to defer interrupts for power saving reasons,
yes?  I was used to seeing FIFO sizes more in the 32-128 bytes, tops.  :-)

      	    	    	   	      - Ted

  reply	other threads:[~2011-02-23 22:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 19:56 How important is it that tty_write_room doesn't lie? Timur Tabi
2011-02-23 20:29 ` Greg KH
2011-02-23 20:48   ` Timur Tabi
2011-02-23 22:57     ` Ted Ts'o [this message]
2011-02-24 12:34       ` Theodore Tso
2011-02-23 23:17     ` Greg KH
2011-02-24 11:29   ` 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=20110223225728.GR2924@thunk.org \
    --to=tytso@mit.edu \
    --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